[GRASS-dev] [release] GRASS 7.2.1 planning

[Martin Landa]

Hi,

2017-02-20 11:07 GMT+01:00 Moritz Lennert <mlennert at club.worldonline.be>:
> Most of these are not bugfixes, but enhancements. I don't think they should
> go into a point release. I'd rather we only fix bugs in point releases and
> get out 7.4 rather quickly if we feel there are enough enhancements.

I fully agree, but what realistically means "quickly"? In good case I
would say one and half year after 7.2.0 release. It means
spring/summer 2018. Eg.

* April 2017 7.2.1
* September 2017 7.2.2
* December 2017 7.2.3
* April 2018 7.2.4
* May 2018 7.4.0
* September 2018 7.2.5 (probably last 7.2.x version)

>From this perspective also small improvements could go to release
branch I would say. Currently we are trying to have 2-3 point release
per year. It means about 4 months release cycle. Lets say:

* first two months - waiting backports (traced at [1]) + small improvements
* second two months - only bugfixes, other backports recorded at [1] -
RFC4 on the road [2]

Note: all backports should be referenced by trac issue if possible

Make sense to you? Ma

[1] https://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing
[2] https://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa