[GenABEL-dev] dealing with suggestions on the devel-list
pirastu at burlo.trieste.it
pirastu at burlo.trieste.it
Fri Mar 11 09:50:56 CET 2011
Dear all,
I think that the procedure seems very straight foward and resonable,
for patches we might want to outline a readme wich should be released with
the patch with some things like what varsion of the GenABEL-dev or CRAN it
was created with and what it does.
Nicola
> * 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