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
20.x release code freeze #40838
Comments
@thaJeztah Any chance you can ping teams in the docker org accordingly? |
@cpuguy83 will do, thanks! |
On the maintainers call, we decided to push freeze another week. |
That will be Friday 5/8. |
What's current status? |
ping @cpuguy83 @thaJeztah |
There's still a few things pending. Not huge things. |
Is there any remaining blocker toward beta? |
We need to revert/change a swarmkit API moby/swarmkit#2965 |
ping @cpuguy83 @thaJeztah |
@Alvise88 Docker is working on cutting a beta now. |
We don't appear to have tags anywhere yet though 😩 |
@tiborvass I think you were working on that (missing tags) ? According to the docker cli: docker/cli@ac365d7 |
Hello @moby/moby-maintainers,
During the last maintainers call, we discussed plans for code freeze for the next release. We've been tracking desired features/changes for a couple of months now and I think we are basically there.
We wanted to ping everyone and set a freeze date for the next release.
The date we discussed is May 1st. This is a forcing function to get the last few changes in.
Please see https://github.com/moby/moby/projects/9 for a list of desirable for this.
If you have a change that is missing that you'd like to have reviewed, please add it.
Also, just to note May 1st is just a date we chose on the call, this can be adjusted as needed but it would be nice to lock this down.
The text was updated successfully, but these errors were encountered: