Question: runc 1.0.0 release plan

[Ace-Tang]

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.

[cyphar]

We were planning to make a 1.0.0 release immediately after 1.0.0-rc5 but that didn't happen. I think that just cutting a release now is as good a choice as any -- though we currently have a pretty bad regression (#1862) that I wouldn't want to include in a release.

[Ace-Tang]

Thanks for the reply soon. I also follow the the discussion about #1862 on the mail list. Wait for your conclusion.

[mikebrow]

#1709

[jameshartig]

Now that the regression has been merged, can a 1.0.0 release be made?

[Ace-Tang]

The 1.0.0 release plan has been discussed in mail list https://groups.google.com/a/opencontainers.org/forum/#!topic/dev/pWEp_UK6aAk

[cyphar]

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.

[AkihiroSuda]

maintainers: any chance to set labels to the issues & PRs that are blocking v1.0.0 ?

[cyphar]

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.

[caniszczyk]

Any thoughts on v1.0 planning for runc? cc: @opencontainers/runc-maintainers

[mrueg]

Can we get a new rc or a proper 1.0 for the recent CVE please?

[cyphar]

I will send around a vote for 1.0.0-rc7 tomorrow morning but I need to go to bed first.

[pigmej]

Hey @cyphar any progress on this?

[cyphar]

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...

[allencloud]

It's unclear to me whether #1979 should be handled first

I think that #1979 should be handled first before releasing official runc 1.0.0. @cyphar