-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
5.0.0-M1 Milestone Plan #2267
Comments
Added recently closed issues and PRs |
Updated delivery targets based on results from latest merge activities. |
Release will not be shipped so removed those milestones. |
So this makes me believe 5.0.0-M1 is not considered GA? Could u clarify what do you understand under GA (General availability)?
If M1 is available in Dockerhub on September 17-th - wouldn't that mean it's GA by all means? |
release = passed QA tests, tagged, and images generated. 5.0.0-M1 is a release. We are partially shipping it. We are not supporting it. We will wait to provide support on it until we get GA, which will be after a series of other milestones that we release and ship |
Milestone Overview
Upgrade and Migration
This is a pre-GA milestone in the new Che 5 stream. Milestones will be sequentially numbered using a M1, M2, Mn notation leading to GA.
Due to a fundamental model change that allows us to deliver multi-machine support, it will only be possible to migrate 4.7.1 workspaces to 5.0.0 at GA (users who wish to try 5.0.0 milestone releases today will have to create new workspaces).
Docker Image Tags
While 5.0 is pre-GA the
:latest
tags on our Docker images will continue to point to 4.7.1. We will also create a new5.0.0-latest
tag to make it easier to try each 5.0.0 milestone release.For more information about our development process please see our development process page.
Schedule
This release will be an Eclipse-signed and marketed release.
Schedule Detail
Code complete milestone
Release candidate created milestone
GitHub release complete (QA verified) milestone
Target Milestone Issues
Epics and Issues
Bugs
The text was updated successfully, but these errors were encountered: