[GenABEL-dev] dealing with suggestions on the devel-list

Yurii Aulchenko yurii.aulchenko at gmail.com
Wed Mar 9 22:17:38 CET 2011


Dear All,

I expect with more people looking at our code we will get more and
more suggestions on how to fix a bug (e.g. Nicola's recent post on
treating 'by.var' problem); we also may expect people posting patches
(this has happened before, when genabel-devel list was not there yet).
It is probably good time to think how we deal with these situations.

What I could think of looks very straightforward to me, but let us
know if you think different

* Situation 1. We get a suggestion.

a) discuss the suggestion on the list
b) if suggestion passes the discussion, a committer submits outline of
bug fix to the bug tracker
c) a committer "assigns" bug to himself (bug tracker)
d) the commiter implements the changes, tests, commit, ... (usual route)

("a committer" refers to anyone who have volunteered, though we
understand that for the near future this will likely be one of the
project coordinators)

* Situation 2. We get a patch.

a) discuss the patch on the list
b) if patch passes the discussion, a committer "assigns" bug to
himself (bug tracker)
c) the committer patch the code, run checks, commit, ... (usual route)

Let me know what you think of the proposed procedure.

best wishes,
Yurii


More information about the genabel-devel mailing list