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

[Diego Fabregat Traver]

Dear all,

this is my first email to the list so "Hello everyone!".

I've never been too involved in the maintenance stage of a software life cycle but the steps suggested by Yurii seem reasonable to me. Which has been the approach so far? Did you already have a bug-tracker? Was the approach successful? If it used to work, I guess there is no need to change it.

I think the possible situations are many. There can be bug reports, patches, feature requests, ... something else? And the way to deal with them probably depends on the number of users/reports you get. If the estimated number of reports is low probably it is possible to handle them in the mailing list, but when the number increases maybe dealing with them through the mailing list may become unmanageable.

Again, I'm not too experienced on software maintenance and I don't know anything about the way the project is organized, so take my words just as mere thoughts :)


Best,
Diego


El 09/03/11, Yurii Aulchenko  <yurii.aulchenko at gmail.com> escribió:

> 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
> _______________________________________________
> genabel-devel mailing list
> genabel-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel