-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release Schedule for 24.11 #339153
Comments
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/24-11-release-cycle-coming-up/51549/1 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
#296953 should be tagged a release blocker. |
@hacscred Seems like that problem has already been fixed. |
GitHub permissions model is not very fine grained. |
It hasn't. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
We've reached the 2nd step in the schedule, all release critical packages are blocked. |
We're in the feature freeze, only non breaking changes now. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Both the nixos:release-24.05 jobset and the nixos:release-24.11 jobset have a negative check interval of -129600 (-36 hours). The check interval of the nixos:release-24.05 jobset changed from 129600 to -129600 within the last day, while the nixos:release-24.11 jobset had a negative check interval for a few days now. Jobsets of older releases still have a positive value. Do you think this is intentional? For five days, the |
I've been managing these manually now. More big 24.11 evals at this point didn't seem worth the delay of #356895 and thus the whole release. EDIT: 24.05 is a bit off topic, but its big channel is blocked on https://hydra.nixos.org/build/279608174#tabs-buildsteps anyway, so we'd again delay other stuff that is not blocked. |
If it's too late already it's too late, but I've been trying to get #357105 merged and backported before release. Is that still realistically possible, or would there be additional evals for the backport PR that would delay things? Edit: Merged, thanks! |
Forgot to mention this yesterday, if it isn't clear or anyone hasn't been on the staging matrix, we have had to delay 24.11 and let a staging cycle go through. There was a regression in curl which broke things and we didn't want it to cause a major impact. |
|
I'm afraid I'd estimate that the next weekend we'll have the binaries and channel including this. |
Maybe make an announcement on Discourse saying the same thing? |
The 24.11 1st staging cycle completed. Thank you @vcunat for getting that through. Saturday, Nov 30th, might end up being the day we get the release out. But that doesn't stop anyone from using it right now, we have the channels up but there's that curl netrc issue plus other possible issues ZHF and others have worked through. |
To be clear, only the |
|
When does the iso file on the https://nixos.org/download/ gets updated? Is it a manual process? |
We just got the infrastructure changes merged 30 seconds ago so I assume that makes it happen. The homepage updates are coming in the next 30 seconds as well. |
master
staging-next
intomaster
, prep for ZHFmaster
master
master
staging-next
fixes into master; begin secondstaging-next
cyclestaging
master
before branch-offmaster
staging-next
fix cyclestaging-next
master
before branch-offmaster
,release-24.11
master
,release-24.11
release-24.11
release-24.11
Note: Dates reflected are in AoE (Anywhere on Earth) time.
The text was updated successfully, but these errors were encountered: