Hi, I do have [some] doubts too on this double master-approach. If there is a feature-frozen old-master 3.9 branch and a new master 3.11 branch, where will most developers be spending their time? Will they be bug-fixing in 3.9 or rather go to 3.11 and send new patches? If new master has the most attraction, this move will not really work (who is testing?). If most people would stick to old master, why start new master in the first place? I just fear that many will go to new master.. Bugs fixed in 3.9 should go up to 3.11; this will be an additional effort. (Small side note: When patches are going up and down, workflow needs to be adjusted?)
So, whatever we do, probably this old problem will always be there.. Much depends on the RM, and better testing :) Marcel Van: [email protected] [mailto:[email protected]] Namens Jared Camins-Esakov Verzonden: woensdag 18 juli 2012 18:51 Aan: Owen Leonard CC: [email protected] Onderwerp: Re: [Koha-devel] About Release process Owen, > - branch the release on git. master goes his way for N+1, major ENH > can be pushed here. N is still controlled by the RM, N-1 controlled by > the RMaint I'm not sure I understand this aspect of it. The branching is to allow enhancements to still be pushed somewhere while what-was-master is in feature freeze? I would think there is some benefit of not pushing any enhancements *anywhere* to encourage folks to be bug-fixing instead. That is correct. As RM presumptive (but perhaps someone else would like to be RM, and eliminate my presumptive status? There's still time :D ), my plan for this period would be to push any enhancements that might be submitted only after bugfixes have been dealt with. Ideally it will be possible to get all submitted enhancements pushed to Master during this period, but given the volume of patches that can precede a release, at my discretion I may delay large features until after the release of 3.10.0. Paul and I discussed this at length, actually. I originally suggested not pushing any large enhancements to master (i.e. 3.11) during the 3.10 feature freeze, but Paul (quite reasonably, I think) argued that not pushing enhancements that were sitting in the queue would not serve to get those developers working on bugfixes, but rather just result in a heavier burden on the RM for 3.12 once 3.10.0 was released. As a compromise, any enhancements that can be pushed will be, but anything that gets in the way of the more important bug fixing will not be pushed until 3.10.0 has left the nest. Hope this clarifies. Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) [email protected]<mailto:[email protected]> (web) http://www.cpbibliography.com/
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
