-
Notifications
You must be signed in to change notification settings - Fork 99
Milestones
Andrés Miguel Rubio edited this page Sep 30, 2021
·
2 revisions
- Our work cadence is split in 4 weeks cycles called milestones.
- The last week is to fix possible defects generated during the regression and stability issues.
- The team will do a milestone planning meeting to add the estimated work scope based on a prioritized backlog.
- During the milestone, the team will be pulling tickets from the TODO column which is sorted by internal rank (priority).
- All the tasks completed during the milestone will be merged into develop.
- When a milestone finishes:
- Release candidate branch will be created from develop freezing the code covered during this milestone.
- After created the release branch, the version code is increased in develop to the next internal version.
- Release candidate branch starts a testing regression to validate the integration of all the tasks.
- Any defect created by the tasks will be fixed over the release candidate branch.
- Any other issue found in the regression will be moved to the backlog in order to be prioritized.
- Once the regression is finished, release branch will be merged into master and master into develop.