[Scaffoldhunter-devel] Making releases more transparent

[Till S. <til...@tu...>]

Hi, 
i would like to propose a more transparent way for release planing, as the main contributers tend to be more distributed all over the world. I suppose to use the bug tracker more extensively for release planing:

I already introduced the new milestones in a previous mail (see attachment). We now tag a bug with "any future version" by default and move this bug to a specific version if we fix the bug or do a release planing. However, it has the drawback, that we do not always know if the next release may be 2.3.1 (only bug fixing) or 2.4.0 (feature release) if we fix a bug. Therefore, we introduce a new Milestone "next release", which should be selected in this case.

If we want to release a new version, there should be a bug report with the title "Scaffold Hunter version X.Y.Z release request". This should give all participants the possibility to discuss show blockers, that should be integrated into the next release and also to determine if we do a feature or bugfix release. We can then simply rename the milestone "next release" to the concrete new version. 

What do you think about this?

Greetings
Till

-- 
Dipl.-Inf. Till Schäfer
TU Dortmund University
Chair 11 - Algorithm Engineering
Otto-Hahn-Str. 14 / Room 237
44227 Dortmund, Germany

e-mail: til...@cs...
phone: +49(231)755-7706
fax: +49(231)755-7740
web: http://ls11-www.cs.uni-dortmund.de/staff/schaefer
pgp: https://keyserver2.pgp.com/vkd/SubmitSearch.event?&&SearchCriteria=0xD84DED79