Document ticketing standards.

LeastAuthority / leastbot

0 stars 0 forks source link

Document ticketing standards. #10

Closed nathan-at-least closed 10 years ago

nathan-at-least commented 10 years ago

Some thoughts:

For any code changes, the code should follow TDD.
A ticket should only be closed when the code which implements is on github's master branch.
A ticket should be closed as soon as its code is on github's master (as opposed to when released or other times).

nathan-at-least commented 10 years ago

Bumped to 0.2.1

nathan-at-least commented 10 years ago

Some revision control convention tie-ins:

Branch names should begin with ${TICKET_NUMBER}.${DESCRIPTION}, and
The only changes to master should be fast-forwards to existing branches, so by implication:
There should be a ticket for every change to master.

nathan-at-least commented 10 years ago

I'm going to mark this as underspecified and close it, because there's not a clear criteria for closing it. We should continue to add conventions here in comments to serve as a conventions guideline, I suppose.