607
edits
Changes
Jump to navigation
Jump to search
Line 37:
Line 37: + + + + + +
no edit summary
When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered.
When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered.
== Bug triaging ==
Module maintainers should ensure that their plans for the release are clearly reflected in the bug tracking system. They are responsible to set milestones and priorities accordingly, in cooperation with the release and the QA teams.
Without making it a strict rule, it would be good if each commit or set of commit would have a ticket associated. The ticket number should be always mentioned in the git log and could also be used to automatically build the list of module changes for the releases.
== Automation ==
== Automation ==
TBD Many of the steps described in this document can be easily automated for maintainers which are using the sugarlabs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.
TBD Many of the steps described in this document can be easily automated for maintainers which are using the sugarlabs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.