-
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
Question: runc 1.0.0 release plan #1905
Comments
We were planning to make a |
Thanks for the reply soon. I also follow the the discussion about #1862 on the mail list. Wait for your conclusion. |
Now that the regression has been merged, can a |
The 1.0.0 release plan has been discussed in mail list https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/pWEp_UK6aAk |
1.0-rc6 was just released, and we have a plan for 1.0 release. The main blocker is spec-compliance and it's something we're working on. |
maintainers: any chance to set labels to the issues & PRs that are blocking v1.0.0 ? |
https://github.com/opencontainers/runc/milestone/7 is the set of blocking issues. There's only two of them, and it's the hooks issues. |
Any thoughts on v1.0 planning for runc? cc: @opencontainers/runc-maintainers |
Can we get a new rc or a proper 1.0 for the recent CVE please? |
I will send around a vote for 1.0.0-rc7 tomorrow morning but I need to go to bed first. |
Hey @cyphar any progress on this? |
It's unclear to me whether #1979 should be handled first. I am working on a patch for it, but I can just send out the vote... |
I will wait until we merge #1984 before doing a release. |
Any blocker for rc7? |
Since runc provides core functionality and is widely used in the container ecosystem, the current situation without an actual release, that fixes the vulnerability, is a bit unsatisfying to me as a downstream (maybe too traditional) packager. I don't feel comfortable picking an (to me arbitrary) commit and provide that snapshot to users of the distribution. Is anyone able to provide some guidance here on well-tested commits? |
While I completely agree in principle (and I will send out a vote for rc7 today), if you package Docker then you are already packaging specific commits -- Docker hasn't used an actual release of runc for at least 3-4 years and if you stayed on the "newest release" then your systems would've been very unstable (and probably insecure). Same goes with containerd. cri-o used to use our releases (back when rc5 and rc6 happened close together) but I think they've also switched to using commits. I'm hoping that after 1.0 we will have more frequent releases -- but the current process of releasing runc (having a 2-week voting process) is absolutely ludicrous and is one of the major reasons we aren't having more frequent releases. We should have a release manager and require only 2 additional LGTMs to do a release (maybe with a mandatory cooling-off period). The spec style of doing releases doesn't make sense for us and never has IMHO. I will bring that up on the ML with the release vote. |
I don't see this vote in https://groups.google.com/a/opencontainers.org/forum/#!forum/dev - am I looking in the wrong place? The rc6 vote seems to have happened there: https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/LCDa1rDyiec |
That is the right mailing list -- I only just got around to sending it just now. Check the list again and you should see the vote announcement. |
Great, here it is: https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/TioIOoxJydk 👍 |
See #2026. 1.0.0-rc7 has been released. |
#2031 seems merged. |
Currently waiting on opencontainers/selinux#51 which fixes the regression we see in |
How long we release a new runc version, 3 months as discussed in mail list before ? |
Post 1.0, we will do regular releases (using a release-manager model where you don't need quorum votes on the mailing list to get releases out). But right now for the 1.0, we still have an issue with post-start hooks and at the moment it looks like we might need a |
Hi @cyphar! Is there a plan to release a new |
Ref. #2074 (comment) cc @thaJeztah I think it may be about time for a new release 😄 |
|
ping @cyphar |
@cyphar What do we need for v1.0.0 GA? |
I think we are basically ready for 1.0 GA. I think one final RC wouldn't be a bad idea, but on the other hand I don't really care if we have to do a |
+1 to 1.0.0 GA thanks for all your hard work! |
I'd like to see the current open PRs in https://github.com/opencontainers/runc/milestone/7 to be merged before v1.0.0. |
There's only two PRs left in the 1.0.0 milestone (one is a cgroupv2 freezer fix, and the other is the cgroupv2 devices bugfix). I'd be happy to send out the vote right afterwards -- now that rc95 has been published with the CVE fix. |
An update -- we planned to do a release last week but a bunch of regressions popped up. I think we've found most of them now so only the PRs currently left in the milestone are needed before I do the release. Hopefully we can do the release next week (it would've been nice to do the release on the 1.0.0-rc1 anniversary, but it seems like these bugs had other plans). |
Hi, maintainers
I want to ask if runc project has plan to make a new release, since I recognize that runc always make a new release almost every six months, do the next new release come out soon? Thanks.
The text was updated successfully, but these errors were encountered: