List view
All new feature development should be complete by the third milestone. It will be at the discretion of each project lead to allow any code changes other than bug fixes after this point. Leads should make these decisions based on the risk introduced by the code change and based on the importance of the feature. The TSC should be consulted if the priorities and risks are unclear.
Due by May 6, 2019•17/17 issues closedNo new features may be proposed for the Capri release without the review and approval of the Technical Steering Committee (TSC) after the second milestone.
Due by March 25, 2019•5/5 issues closedThis first milestone serves as a checkpoint on the progress so far and as a good point to make sure our release processes are in order.
Due by February 3, 2019•2/2 issues closedA release candidate will be done the week of November 26. The RC code should be the focus of all test efforts leading up to the final release. Only critical bug fixes should be allowed to be merged after this point to ensure the final release is in good shape.
Due by November 26, 2018The third Bali milestone will be the week of November 5. All new feature development should be complete by the third milestone. It will be at the discretion of each project lead to allow any code changes other than bug fixes after this point. Leads should make these decisions based on the risk introduced by the code change and based on the importance of the feature. The TSC should be consulted if the priorities and risks are unclear.
Due by November 5, 2018•5/5 issues closedThe second Bali milestone will be the week of September 24. No new features may be proposed for the Bali release without the review and approval of the Technical Steering Committee (TSC) after the second milestone.
Due by September 24, 2018•4/4 issues closedThe is the first beta version of opensds controller project.
Due by December 15, 2017•26/26 issues closed