Compiz Core branching and release strategy
A *suggestion* of how Compiz Core branches should be structured and maintained starting with the 0.9.7.0 release.
Blueprint information
- Status:
- Complete
- Approver:
- Daniel van Vugt
- Priority:
- Undefined
- Drafter:
- Daniel van Vugt
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Daniel van Vugt
- Completed by
- Daniel van Vugt
Related branches
Related bugs
Sprints
Whiteboard
DURING PRECISE DEVELOPMENT:
* Create a new series called 0.9.7
* Set lp:compiz-core to point to the new 0.9.7 series
* All fixes go to lp:compiz-core (series 0.9.7)
* Release 0.9.7.0 will be completed and tagged in the 0.9.7 series
* Periodic releases 0.9.7.N prior to precise code freeze.
* Merge compiz-
* Merge all plugins into compiz-plugins (LP #923572)
AFTER PRECISE CODE FREEZE:
* Create a new series called 0.9.8 (or higher)
* Set lp:compiz-core to point to the new 0.9.8 series
* All stable and safe fixes go into both series 0.9.8 and 0.9.7
* All new features and non-trivial fixes go into 0.9.8 only
* Periodic releases 0.9.7.N from the 0.9.7 series for precise maintenance
(~smspillaz) Agreed, although really the stable series should be 0.9.8 and the unstable should be 0.9.9
(~vanvugt) Are we sure we want to squeeze LP #923695 in so soon? If it's optional then I think it should be deferred. We're out of time. I know LP #923572 needs to be in precise (or else we lose all the plugins fixes from the last few months)
Work Items
Work items:
[vanvugt] Do it: DONE
