Hi devs,
since GRASS GIS is a truly long term project (remember its 33rd
"birthday" on July 29th!) we need to get out version 6.4.6. See also
the
https://trac.osgeo.org/grass/roadmap
A few relevant fixes got accumulated in the 6.4 release branch, so
time to publish a new minor release.
Following our proposed
http://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure
the release procedure would be:
Step 1 - Proposal of release: Done.
Step 2 (day X) - Soft freeze of release branch: suggestion 6 July 2016 
Step 3 (X+30 days) - Hard freeze & RC1:
[important at least for the winGRASS package]
... etc according to RFC4.
Coordination is done here:
http://trac.osgeo.org/grass/wiki/Grass6Planning
To collect the changes I have started a News page at:
https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
Suggestion: if nobody has complex submissions to be done, we may even
shorten step 2 to less than 30 days.
Best,
Markus
--
Markus Neteler
http://www.mundialis.de - free data with free software
http://grass.osgeo.org
http://courses.neteler.org/blog
On Tue, Jul 5, 2016 at 4:46 PM, Markus Neteler <neteler@osgeo.org> wrote:
Hi devs,
since GRASS GIS is a truly long term project (remember its 33rd
"birthday" on July 29th!) we need to get out version 6.4.6. See also the
https://trac.osgeo.org/grass/roadmap
A few relevant fixes got accumulated in the 6.4 release branch, so
time to publish a new minor release.
Following our proposed
http://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure
the release procedure would be:
Step 1 - Proposal of release: Done.
Step 2 (day X) - Soft freeze of release branch: suggestion 6 July 2016
Well, now we are 16th of July.
Step 3 (X+30 days) - Hard freeze & RC1:
[important at least for the winGRASS package]
... etc according to RFC4.
Coordination is done here:
http://trac.osgeo.org/grass/wiki/Grass6Planning
To collect the changes I have started a News page at:
https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
For the record: I have just made three important backports in
r.terraflow and libiostream:
r68988 + r68989 + r68990
which fix compilation issues with GCC 6.
Please test.
Suggestion: if nobody has complex submissions to be done, we may even
shorten step 2 to less than 30 days.
I'm still of that opinion.
Best,
Markus
--
Markus Neteler
http://www.mundialis.de - free data with free software
http://grass.osgeo.org
http://courses.neteler.org/blog
Hi,
2016-07-17 0:02 GMT+02:00 Markus Neteler <neteler@osgeo.org>:
Suggestion: if nobody has complex submissions to be done, we may even
shorten step 2 to less than 30 days.
I'm still of that opinion.
+1 Martin
--
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
Hi,
gentle reminder that the 6.4.6 release is due.
Coordination is done here:
http://trac.osgeo.org/grass/wiki/Grass6Planning
Open bugs concerning GRASS 6.x
https://trac.osgeo.org/grass/report/16
News page (to be completed) at:
https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
Any objections to prepare RC1?
Markus
On Thu, Aug 11, 2016 at 11:18 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
gentle reminder that the 6.4.6 release is due.
Coordination is done here:
http://trac.osgeo.org/grass/wiki/Grass6Planning
Open bugs concerning GRASS 6.x
https://trac.osgeo.org/grass/report/16
News page (to be completed) at:
https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
Any objections to prepare RC1?
Now available at
https://grass.osgeo.org/grass64/source/
--> https://grass.osgeo.org/grass64/source/grass-6.4.6RC1.tar.gz
Please test it!
Markus
On 17/08/16 09:30, Markus Neteler wrote:
On Thu, Aug 11, 2016 at 11:18 AM, Markus Neteler <neteler@osgeo.org> wrote:
Hi,
gentle reminder that the 6.4.6 release is due.
Coordination is done here:
http://trac.osgeo.org/grass/wiki/Grass6Planning
Open bugs concerning GRASS 6.x
https://trac.osgeo.org/grass/report/16
News page (to be completed) at:
https://trac.osgeo.org/grass/wiki/Release/6.4.6-News
Any objections to prepare RC1?
Now available at
https://grass.osgeo.org/grass64/source/
--> https://grass.osgeo.org/grass64/source/grass-6.4.6RC1.tar.gz
Please test it!
The release having been tagged and source code already available, what is left that needs to be done for releasing 6.4.6 ?
Moritz
On Mon, Aug 29, 2016 at 3:16 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...
The release having been tagged and source code already available, what is
left that needs to be done for releasing 6.4.6 ?
I have the announcement almost done. So, sit & wait that I get a
moment later today to upload the stuff
The FOSS4G 2016 only ended yesterday, hence the delay.
Markus
On 29/08/16 15:19, Markus Neteler wrote:
On Mon, Aug 29, 2016 at 3:16 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...
The release having been tagged and source code already available, what is
left that needs to be done for releasing 6.4.6 ?
I have the announcement almost done. So, sit & wait that I get a
moment later today to upload the stuff
The FOSS4G 2016 only ended yesterday, hence the delay.
It was not a critique of the delay, but a inquiry to know if you need help with anything. 
Moritz
On Mon, Aug 29, 2016 at 5:20 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
On 29/08/16 15:19, Markus Neteler wrote:
On Mon, Aug 29, 2016 at 3:16 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...
The release having been tagged and source code already available, what is
left that needs to be done for releasing 6.4.6 ?
I have the announcement almost done. So, sit & wait that I get a
moment later today to upload the stuff
The FOSS4G 2016 only ended yesterday, hence the delay.
It was not a critique of the delay, but a inquiry to know if you need help
with anything.
Sure, no problem! In general help is seeked to share the workload of
posting the announcement as a press release.
The doc/howto_release.txt in the course code contains the links. BUT:
I can happily do that since it is the end of GRASS GIS 6 releases
anyway, so no big hype is needed here. Also the creation of binaries
is less important here perhaps.
Getting related help for the next G7 releases would be great, i.e.
- write a catchy announcement
- add nice screenshot(s) to it
- provide binaries.
However, we may discuss that in the 7.0.5 planning email thread to not
mix it up with this one here.
thanks
Markus