Meeting Minutes 07.05.2016
Here are the notes of product meeting July 5th, 2016. ######TOPICS DISCUSSED:
- Pre-Ship / Post-Ship for 4.3/4.4
- Status on 4.5 Release
- Scope for 4.6
- Discuss management of public issues
- Reformatting all executions of che to always be container-based.
######ACTION ITEMS:
- Create pre-ship docs issues for 4.5 (Stevan)
- Create UI issue for new Consoles designs (Stevan)
- Estimate and plan all issues from 4.5 scope in next sprint (TLs)
- Labels definition (Tyler/Brad)
- Add issue template for Codenvy repo (Eugene)
######IMPORTANT POINTS ON TOPICS DISCUSSED:
0. Pre-Ship / Post-Ship for 4.3 / 4.4
They were not all solved in time due to certain circumstances:
- support for redhat dev nation (Eugene, Brad)
- support for 4.4 release
- eclipse democamp (Stevan)
Now the situation has been handled.
1. Status for 4.5 Release
Dashboard has been cleanup. Bugs have been reviewed and scope narrowed. Target cleared.
4.5 : release date planned for 12 July
4.5 will introduce the new URL, so we'll need to go trough all the various references in the docs for Che and Codenvy.
2. Scope for 4.6
- Stacks/Templates not ready
- New console tabs
- UI for new list in dashboard
- move to github issues
3. Discuss management of public issues
An issue template has been added to Che repository/ we'll do the same for Codenvy repo.
A new sprint will start on August 3rd. First sprint that should be done entirely on github. We'll move all issues to github and follow new processes. We'll scope 4.6 and move all the issues from Jira.
A clear definitions about labels + milestone will be documented and discussed.
4. Reformatting all executions of che to always be container-based.
A discussion occurred about how to simplify the overall setup of Che and upgrade cycle. One of the potential solution would be to support a single server mode, when it runs inside of a Che container.
Link to a study: https://docs.google.com/document/d/14Z9q8g-wiZWlqaY0L_62GuVuSGKgO20BhA_iamB7INk/edit