Skip to content

Latest commit

 

History

History
26 lines (25 loc) · 1.41 KB

development_process.md

File metadata and controls

26 lines (25 loc) · 1.41 KB

Development process

  1. Find a ticket from the top of To Do column on Active Development (Kanban board)
  2. Assign it to yourself
  3. Move it to In progress
  4. Create a feature branch off master
  5. Do the work
  6. Get all tests green locally
  7. Push branch to origin, eg. git push -u origin my_feature_branch
  8. Check automated tests for branch pass (no conflicts, CircleCI, RuboCop)
  9. Create a PR
  10. Move ticket to Needs review on Kanban board
  11. Get PR reviewed and approved
  12. Merge down to master
  13. Discuss if it's a reasonable time to merge to staging
  14. Merge to staging
  15. Move ticket to Awaiting QA on Kanban board
  16. Communicate with team about test plan for new stuff on staging
  17. Move tickets to QA Accepted on Kanban board
  18. Release manager checks with team that we're good to promote staging to production
  19. Merge staging to production
  20. Create a tag, Eg. git tag -a v5.0.3 -m 'An annotated tag'
  21. Go into semaphore and do a manual deploy
  22. Sanity check on production that core flows work, and review features
  23. Release manager moves tickets from QA Accepted to Released
  24. Delete feature branches once they are in the tag