-
Notifications
You must be signed in to change notification settings - Fork 2.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
Roadmap for registry:2.7.2 and beyond #3311
Comments
@stevvooe @dmcgowan @BrianBland @aaronlehmann I see that you guys are top committers for this project, can anyone of you please clarify about the sustainability of this project i.e. can we take dependency on this project to setup docker private registry for hosting images onprem |
The v2.7.2/v2.8 is planned, but we don't have a ETA about it. Hopefully we can have a 2.7.2 soon. |
we had already commits, is there any way the current state of things can be released as a new version? it would be kinda nice to have a new release of things at least every 6 months. |
Guys is there an update on it? |
We will do We are working on getting the "edge" ( |
Closing this issue as v2.8.2 is currently the latest release and this doesn’t seem relevant anymore. |
registry:2.7.1 was released on January 17 2019 there seems to have been a more recent image published on docker hub though.
The ROADMAP.md was last updated 5 years ago.
I can see commits happening, but issues like #3189 that have not had any response have me wondering what the future of this project is. As someone who is new to docker this is concerning to me, as having a reliable/robust registry infrastructure seems to be central to implementing any sort of container workload in any sort of production capacity.
The text was updated successfully, but these errors were encountered: