Skip to content
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

Closed
55 of 57 tasks
bmicklea opened this issue Aug 30, 2016 · 5 comments
Closed
55 of 57 tasks

5.0.0-M1 Milestone Plan #2267

bmicklea opened this issue Aug 30, 2016 · 5 comments
Assignees
Labels
kind/planning A checklist of issues for planning a particular sprint.
Milestone

Comments

@bmicklea
Copy link

bmicklea commented Aug 30, 2016

Milestone Overview

  • Multi-machine workspaces with YAML syntax
  • Bitnami pre-built stacks for additional languages
  • Workspace agents to allow any Docker image to work in Che without additional syntax
  • Che launcher profiles to simplify managing multiple Che configurations on the same machine
  • Updated editor to Orion 12

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

  • Code complete milestone: September 14, 2016
  • GitHub release complete (QA verified) milestone: September 16, 2016
  • Ship milestone: September 17, 2016

Schedule Detail

Code complete milestone

  • Milestone issues complete
  • Smoke tests started

Release candidate created milestone

  • Release candidate created
  • Test cycles started
  • Docs complete

GitHub release complete (QA verified) milestone

  • Release completed and QA verified
  • Release notes updated
  • Final release information updated on GitHub
  • Docs reviewed and live
  • Release Docker images available (5.0.0-M1 tag)

Target Milestone Issues

Epics and Issues

Bugs

@bmicklea bmicklea added the kind/planning A checklist of issues for planning a particular sprint. label Aug 30, 2016
@bmicklea bmicklea added this to the 4.8.0 milestone Aug 30, 2016
@bmicklea bmicklea self-assigned this Aug 30, 2016
@bmicklea
Copy link
Author

bmicklea commented Sep 1, 2016

Added recently closed issues and PRs

@bmicklea
Copy link
Author

bmicklea commented Sep 2, 2016

Updated delivery targets based on results from latest merge activities.

@bmicklea
Copy link
Author

bmicklea commented Sep 6, 2016

Release will not be shipped so removed those milestones.

@bmicklea bmicklea changed the title Che Milestone 4.8.0 4.8.0 Milestone Plan Sep 6, 2016
@bmicklea bmicklea changed the title 4.8.0 Milestone Plan 5.0.0-M1 Milestone Plan Sep 6, 2016
@linuxd3v
Copy link

linuxd3v commented Sep 14, 2016

Subsequent milestones leading to GA will be numbered with sequential M2..Mn notation.

So this makes me believe 5.0.0-M1 is not considered GA? Could u clarify what do you understand under GA (General availability)?

Ship milestone: September 17, 2016

If M1 is available in Dockerhub on September 17-th - wouldn't that mean it's GA by all means?

@TylerJewell
Copy link

release = passed QA tests, tagged, and images generated.
shipped = items made available on dockerhub, eclipse servers, and codenvy systems
ga = supported with hotfixes, github issues, etc.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/planning A checklist of issues for planning a particular sprint.
Projects
None yet
Development

No branches or pull requests

3 participants