Skip to content

Redmine workflow.md

Jump to bottom
kathi-fletcher edited this page Mar 10, 2013 · 4 revisions

Milestones and Tickets

We organize work into milestones and tickets. The milestones represent related work or work that is targeted for a particular release date or event.

Commits referencing tickets

Commits to github should reference related tickets. When developers are fixing bugs or adding ticketed features, they should reference the ticket in the commits as explained here: Referencing-issues-in-commit-messages.

We may want to clarify ways to reference pull requests to tickets.

Ticket workflow

In general tickets pass through the following workflow

new -> in progress -> (developer done) -> testing -> (failed testing) -> closed

State clarifications

  • in progress: the tickets is being worked on. developers should assign themself to the ticket
  • developer done: this is an optional state to be used if the work is done, but the developer cannot get the fix on the testing server. Don't bother with this state if the ticket is on the testing server.
  • testing : the ticket fix should be on the testing.oerpub.org server. It can also be on another testing server, in which case the server's name should be included in the last comment to the ticket.
  • closed : Right now the closed state means that testing has passed, but it doesn't say anything about whether the fix has been merged to the stable branch and released. We may try to clarify this in the future.
Clone this wiki locally