2018-03-09 8:53 GMT+01:00 Markus Neteler <neteler@osgeo.org>:
If there are no objections, I'll package 7.2.3RC1 tonight or tomorrow.
no objection. Probably too radical, but do we really need RCs for 7.2
point release? Recently 7.0.6 version has been released without any
RC. It make sense to be. Let's keep RC policy only for latest major
release (7.4). What do you think?
2018-03-09 8:53 GMT+01:00 Markus Neteler <neteler@osgeo.org>:
If there are no objections, I'll package 7.2.3RC1 tonight or tomorrow.
no objection.
None from me either.
Probably too radical, but do we really need RCs for 7.2
point release? Recently 7.0.6 version has been released without any
RC. It make sense to be. Let's keep RC policy only for latest major
release (7.4). What do you think?
If we are disciplined in terms of limiting any backports to the old stable line (i.e. 7.2) to pure bugfixing then +1.
I also think that we should officially stop the 7.0 line. I would favour a policy of oldoldstable (now 7.0) gets one last bugfix release when a new stable release comes out (7.4). Oldstable (7.2) gets bugfix releases until it becomes oldoldstable (i.e. when 7.6 or 8 is released).
Concerning the release news: if we have nothing to report in some subsections should we keep them, but empty (e.g. "Improvements in the Graphical User Interface" and "Scripting") or should we just delete these subsections ?
If there are no objections, I’ll package 7.2.3RC1 tonight or tomorrow.
no objection.
None from me either.
Probably too radical, but do we really need RCs for 7.2
point release? Recently 7.0.6 version has been released without any
RC. It make sense to be. Let’s keep RC policy only for latest major
release (7.4). What do you think?
If we are disciplined in terms of limiting any backports to the old stable line (i.e. 7.2) to pure bugfixing then +1.
I also think that we should officially stop the 7.0 line. I would favour a policy of oldoldstable (now 7.0) gets one last bugfix release when a new stable release comes out (7.4). Oldstable (7.2) gets bugfix releases until it becomes oldoldstable (i.e. when 7.6 or 8 is released).
Concerning the release news: if we have nothing to report in some subsections should we keep them, but empty (e.g. “Improvements in the Graphical User Interface” and “Scripting”) or should we just delete these subsections ?
On Fri, Mar 9, 2018 at 10:54 AM, Martin Landa <landa.martin@gmail.com> wrote:
2018-03-09 8:53 GMT+01:00 Markus Neteler <neteler@osgeo.org>:
If there are no objections, I'll package 7.2.3RC1 tonight or tomorrow.
no objection. Probably too radical, but do we really need RCs for 7.2
point release? Recently 7.0.6 version has been released without any
RC. It make sense to be. Let's keep RC policy only for latest major
release (7.4). What do you think?
I am not convinced - a single RC would be good to avoid emergency re-release.
Maybe no fully packaging needed but know if it compiles at all...
RC then should be a real RC. If it compiles and installs on
Windows/one Linux, ship it! (mv grass-rc.tgz grass-release.tgz) No
"yet another RC in three weeks".
Māris.
2018-03-09 16:14 GMT+02:00 Markus Neteler <neteler@osgeo.org>:
I am not convinced - a single RC would be good to avoid emergency re-release.
Maybe no fully packaging needed but know if it compiles at all...
RC then should be a real RC. If it compiles and installs on
Windows/one Linux, ship it! (mv grass-rc.tgz grass-release.tgz) No
“yet another RC in three weeks”.