-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Blockers for v1.2.0 #4114
Comments
We don't have timeline for v1.2.0, but we should try to release v1.2.0 by the end of the year. |
Well, we have the 1.2.0 milestone (which I am trying comb through regularly), and everything that's in there is kind of a blocker for 1.2.0. Feel free to modify milestones for any issues/PRs, but at the very least we have one more blocker:
|
Not everything. |
Well, strictly speaking, everything that is under that milestone needs to either be included into 1.2.0, or be reassigned to a different milestone. Whis is why I said
|
I still think #3985 is needed for 1.2.0. There are several issues with mount propagation (not to mention the serious restriction of idmapped mounts) that are fixed with #3985. We also need #3990 if we want to make sure people scream at us during the -rc1 if it breaks something. Other than those, I don't have any strong opinions on any remaining PRs. |
Given that it took well over 3 years to get 1.1.0 finished (incl. half a year from rc1 to GA), is it really necessary (resp. judicious) to block runc 1.2 on a spec-release? |
Necessary, because we have been depending on its main branch: |
This task has been done 👍
|
Hi guys, Eagerly waiting for that 1.2 release with fixes on mount options. What do you think is a realistic release date? Thanks |
Ping |
I think we are ready to release rc.2, and release GA after verifying compatibility with Docker, containerd, BuildKit, etc. cc @opencontainers/runc-maintainers |
Turned out that we need to make a decision on this one too |
Blockers for rc.1 (#3963):
Blockers for GA:
v1.1.1v1.2.0 Release v1.2.0 runtime-spec#1242@opencontainers/runc-maintainers Feel free to edit this issue
The text was updated successfully, but these errors were encountered: