masterreflects the version in production.developreflects the version in staging and contains the features and bug fixes need for the next milestonemasteris updated when releasing the current milestone (develop -> master), and for the occasional hotfix.
- Features issues are created as individual Github issues.
- Features issues are grouped into
Epics(see current list of Epics). Epics should ideally contain a user story and acceptance tests, as well as list of attached bugs and features, and when applicable a API spec. - Feature issues are to be closed when the code is merged into develop. This can be done automatically (reference to the issue number in a commit) or manually. If despite code review, a feature is not considered done, a new issue should be opened as a
Bug.
- Open an issue, attaching the label
bug. (see current list of bugs) - A bug report should contain steps to reproduce, environment tested and when relevant screenshots, animated screenshots, browser specs.
- When applicable, the issue is attached to an Epic.
- When applicable, the issue is attached to a Milestone.
- Bug issues are to be closed when the code is merged into develop or master.