[pio-develop] Proposed workflow

Hello developers,

In bug 278 Micah Bunting wrote:
> I wanted to work more on it, but time was not on my side. My weekend
started just after the bug was fixed.

Let's agree on a workflow. This is the workflow that Bas Wijnen and I
used when both of us were actively working on Pioneers/Gnocatan:

When one of us wants to work on a bug/patch/feature, set the 'Owner'
field to yourself. That is a signal that the issue is claimed, and that
the other developers will not need to look into that issue. If you have
ideas, either post to the issue or mail pio-develop.

When the patch is ready, it can either be directly committed (after a
'make reindent') or it can be attached to the issue, depending on the
expected amount of comments. I think that large/complex patches can best
be attached to the issue. When I was very busy developing with Bas
Wijnen, we agreed on a three day period. After that period the patch
could be committed, before that, is was up for review. (If the review
finished earlier, the commit could be done earlier).

Bas and I also used the following:
- Developer A writes the patch
- Developer B writes the ChangeLog (using the name of developer A) and
commits.
I now think it is better to commit your own patches, it also shows up
better with 'svn praise'. :-)

Which workflow is chosen depends on personal taste and available time.
At this moment I have much time available, but that might change at any
time.

With kind regards,
Roland Clobus