[GRASS-PSC] releases schedule

Vaclav Petras wenzeslaus at gmail.com
Tue Apr 1 07:46:50 PDT 2014


On Mon, Mar 31, 2014 at 11:40 AM, Vaclav Petras <wenzeslaus at gmail.com>
 wrote:

>
>> I find that 6 months is a fairly long period to maintain a bugfix-only
>> branch. I would rather propose to either branch later, or to allow more
>> than just bugfixes into the release branch for 4-5 months before going into
>> bugfix-only phase for the last month or two. During the first period new
>> features can be ported to the release branch once they have had some
>> testing in trunk.
>>
>>
> Moritz, I believe that these are two different things.
>
> ...
>
> Second, committing features to both branches is what is taking the time
> from us and creating uncertainty about what is where and what are the
> branches for. I think that this is crucial point and the lengths of time
> periods above should be decided based on this, not the other way around.
>
> On Mon, Mar 31, 2014 at 11:09 PM, Yann Chemin <ychemin at gmail.com> wrote:

> It looks like we all want to see version numbers move on a yearly basis
> with periods of branching and periods of releasing...


We need to agree on the policy of committing to release branch(es). See my
proposal [1] for details.

[1] http://lists.osgeo.org/pipermail/grass-psc/2014-March/001150.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-psc/attachments/20140401/fad5a3e9/attachment.html>


More information about the grass-psc mailing list