[GRASS-dev] 6.4.4 planning

cmbarton · December 17, 2013, 10:02pm

I started compiling GRASS 6.4, release branch last Friday but was only able to test it today. It seems to work fine under Mavericks for Mac.

Here are a couple a minor issues I noticed.

When I first tried to use nviz (3D display), it failed, with an error message in the console. But it worked fine every time since then, even after restarting GRASS.

Also, there is chatter in the terminal on opening nviz.

GRASS_INFO_MESSAGE(75334,4): Loading raster map elevation@PERMANENT…
GRASS_INFO_END(75334,4)

GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9
…

and

GRASS_INFO_MESSAGE(75334,6): Translating colors from raster map elevation@PERMANENT…
GRASS_INFO_END(75334,6)

GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9

Probably a simple fix if you know where to find it.

MIchael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ 85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://csdc.asu.edu, http://shesc.asu.edu
http://www.public.asu.edu/~cmbarton

On Dec 12, 2013, at 11:32 PM, Michael Barton <Michael.Barton@asu.edu> wrote:

At the moment, GRASS 6.5 is not compiling on the Mac under OS X 10.9 (Mavericks).

Michaesl

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)

www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu

On Dec 12, 2013, at 11:23 PM, grass-dev-request@lists.osgeo.org wrote:

From: Markus Neteler <neteler@osgeo.org>

Subject: Re: [GRASS-dev] 6.4.4 planning

Date: December 12, 2013 at 3:01:22 PM MST

To: GRASS developers list <grass-dev@lists.osgeo.org>

On Sun, Nov 24, 2013 at 4:32 PM, Helmut Kudrnovsky <hellik@web.de> wrote:

Markus Neteler wrote

On Sat, Nov 16, 2013 at 3:00 AM, Hamish

on the grass-user ML Markus N wrote:

(and it is time to get 6.4.4 out…)

“Important bugs concerning the next release”
https://trac.osgeo.org/grass/report/13

…

see http://trac.osgeo.org/grass/ticket/2138 for the actual state of python
addons in winGRASS6.5.svn/6.4.svn.

we are near to working python addon scripts in winGRASS

this seem to be the one and only thing blocking 6.4.4RC1…
Any suggestions to get it done?

Markus

neteler · January 12, 2014, 9:24pm

On Tue, Dec 17, 2013 at 11:02 PM, Michael Barton <Michael.Barton@asu.edu> wrote:
...

Also, there is chatter in the terminal on opening nviz.

GRASS_INFO_MESSAGE(75334,4): Loading raster map <elevation@PERMANENT>...
GRASS_INFO_END(75334,4)

GRASS_INFO_PERCENT: 0
GRASS_INFO_PERCENT: 3
GRASS_INFO_PERCENT: 6
GRASS_INFO_PERCENT: 9
…

There is a similar ticket open:

https://trac.osgeo.org/grass/ticket/312

How to catch this GRASS_INFO_PERCENT output?

Markus

neteler · February 1, 2014, 10:33pm

Hi devs,

some time passed, so we should push RC1 out of the door:

Please check:

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

and please help to complete the draft release notes:
https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

thanks
Markus

neteler · April 20, 2014, 5:38pm

Hi devs,

in order to prepare the 6.4.4RC1, please check:

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

I have updated to some extent the draft release notes (please add more):
https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

Markus

neteler · April 29, 2014, 4:29pm

Hi,

On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler <neteler@osgeo.org> wrote:

Hi devs,

in order to prepare the 6.4.4RC1, please check:

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

now v.buffer has been fixed by Markus Metz (using the GEOS library).

Please test.

I have updated to some extent the draft release notes (please add more):
https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

Markus

martinl · May 3, 2014, 7:42pm

Hi,

2014-04-29 18:29 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

now v.buffer has been fixed by Markus Metz (using the GEOS library).

Please test.

I have updated to some extent the draft release notes (please add more):
https://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

cool, I would say that it's time for RC1... Martin

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

neteler · May 5, 2014, 6:52pm

On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler <neteler@osgeo.org> wrote:

in order to prepare the 6.4.4RC1, please check:

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

Here the full list of issues but none is a blocker:
https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4

Ready to tag RC1, I would say.

Markus

martinl · May 5, 2014, 6:54pm

Hi Markus,

2014-05-05 20:52 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

Ready to tag RC1, I would say.

one big +1. Martin

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

neteler · May 14, 2014, 10:56pm

On Mon, May 5, 2014 at 8:52 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler <neteler@osgeo.org> wrote:

in order to prepare the 6.4.4RC1, please check:

Draft announcement to be updated:
http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

Here the full list of issues but none is a blocker:
https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4

Here some relevant ones:

To test on Windows:

r.kappa: call to r.stats fails if spaces in path
https://trac.osgeo.org/grass/ticket/2116

g.remove cannot remove vector map because of space in DB layer name
https://trac.osgeo.org/grass/ticket/1438

---------
v.external gui exceeds the border of the screen
https://trac.osgeo.org/grass/ticket/2159

r.univar NaN
https://trac.osgeo.org/grass/ticket/2269

---------
r.walk backport
https://trac.osgeo.org/grass/ticket/1628

v.kcv backport
https://trac.osgeo.org/grass/ticket/2035

Perhaps some could be done before tagging RC1?

Markus

neteler · May 15, 2014, 9:14pm

On Thu, May 15, 2014 at 12:56 AM, Markus Neteler <neteler@osgeo.org> wrote:

On Mon, May 5, 2014 at 8:52 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler <neteler@osgeo.org> wrote:

in order to prepare the 6.4.4RC1, please check:

Draft announcement to be updated:
http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

Here the full list of issues but none is a blocker:
https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4

Here some relevant ones:

Thanks for having solved some of the issues in the past 24 hours.

To test on Windows:
g.remove cannot remove vector map because of space in DB layer name
https://trac.osgeo.org/grass/ticket/1438

... to be tested.

---------
r.univar NaN
https://trac.osgeo.org/grass/ticket/2269

... missing output to be changed (all GRASS versions).

---------
r.walk backport
https://trac.osgeo.org/grass/ticket/1628

... not sure what to backport.

v.kcv backport
https://trac.osgeo.org/grass/ticket/2035

... any objections to submit the patch?

And/or I can tag RC1 now and we do these issues later.

Markus

mlennert · May 16, 2014, 12:38pm

On 15/05/14 23:14, Markus Neteler wrote:

On Thu, May 15, 2014 at 12:56 AM, Markus Neteler <neteler@osgeo.org> wrote:

On Mon, May 5, 2014 at 8:52 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Tue, Apr 29, 2014 at 6:29 PM, Markus Neteler <neteler@osgeo.org> wrote:

On Sun, Apr 20, 2014 at 7:38 PM, Markus Neteler <neteler@osgeo.org> wrote:

in order to prepare the 6.4.4RC1, please check:

Draft announcement to be updated:
http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

Here the full list of issues but none is a blocker:
https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4

Here some relevant ones:

Thanks for having solved some of the issues in the past 24 hours.

To test on Windows:
g.remove cannot remove vector map because of space in DB layer name
https://trac.osgeo.org/grass/ticket/1438

You note that this should be wontfix. What do you want to be tested ?

r.univar NaN
https://trac.osgeo.org/grass/ticket/2269

... missing output to be changed (all GRASS versions).

I see this more as an enhancement request than a bug. I don't think this should hold up a release.

---------
r.walk backport
https://trac.osgeo.org/grass/ticket/1628

... not sure what to backport.

v.kcv backport
https://trac.osgeo.org/grass/ticket/2035

... any objections to submit the patch?

See my comment in the ticket.

And/or I can tag RC1 now and we do these issues later.

I think that except for the r.walk segfault, none are really showstoppers. And even that only seems to be reproducible in a very specific situation.

Moritz

neteler · May 25, 2014, 7:32am

On Fri, May 16, 2014 at 2:38 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

On 15/05/14 23:14, Markus Neteler wrote:

...

Draft announcement to be updated:
http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

Here the full list of issues but none is a blocker:

https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4

To test on Windows:
g.remove cannot remove vector map because of space in DB layer name
https://trac.osgeo.org/grass/ticket/1438

You note that this should be wontfix. What do you want to be tested ?

Right, nothing to be tested I guess. To be closed?

r.univar NaN
https://trac.osgeo.org/grass/ticket/2269

... missing output to be changed (all GRASS versions).

I see this more as an enhancement request than a bug. I don't think this
should hold up a release.

ok.

---------
r.walk backport
https://trac.osgeo.org/grass/ticket/1628

... not sure what to backport.

Markus Metz may have an idea.

v.kcv backport
https://trac.osgeo.org/grass/ticket/2035

See my comment in the ticket.

The vector overwrite issue in other mapsets seems to be a general
problem, see ticket.

And/or I can tag RC1 now and we do these issues later.

I think that except for the r.walk segfault, none are really showstoppers.
And even that only seems to be reproducible in a very specific situation.

Given the recent discussion elsewhere I am stuck here.
Do you want me to tag RC1 or wait ...?

Markus

mlennert · May 26, 2014, 10:58am

On 25/05/14 09:32, Markus Neteler wrote:

On Fri, May 16, 2014 at 2:38 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

On 15/05/14 23:14, Markus Neteler wrote:

...

Draft announcement to be updated:
http://trac.osgeo.org/grass/wiki/Release/6.4.4RC1-News

"Important bugs concerning the next release"
https://trac.osgeo.org/grass/report/13

Here the full list of issues but none is a blocker:

https://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=status&milestone=6.4.4

To test on Windows:
g.remove cannot remove vector map because of space in DB layer name
https://trac.osgeo.org/grass/ticket/1438

You note that this should be wontfix. What do you want to be tested ?

Right, nothing to be tested I guess. To be closed?

Yes.

---------
r.walk backport
https://trac.osgeo.org/grass/ticket/1628

... not sure what to backport.

Markus Metz may have an idea.

v.kcv backport
https://trac.osgeo.org/grass/ticket/2035

See my comment in the ticket.

The vector overwrite issue in other mapsets seems to be a general
problem, see ticket.

Yes, and I think this is serious enough to solve this before release, even if people seem to have lived with it for a long time...

And/or I can tag RC1 now and we do these issues later.

I think that except for the r.walk segfault, none are really showstoppers.
And even that only seems to be reproducible in a very specific situation.

Given the recent discussion elsewhere I am stuck here.
Do you want me to tag RC1 or wait ...?

I think that we should try to structure the entire release process a bit more as we are currently dealing with two release processes in parallel (6 and 7) and I have the feeling that this is a bit overwhelming for our little team and that the lack of clear structure of the process leads to the frustrations seen on the list lately.

I would, therefore, propose to focus on 6.4.4 for now, getting that out of the door before we work on 7.0 (especially since there seem to be some fundamental issues to be solved before releasing anything).

I also think that we should work out a clear calendar for that release with official announcements of freeze policy.

I think we are not far at all from releasing, so maybe something like this:

- Real freeze of grass64_release at the end of this week. This means that any backports from grass6_devel should happen before that moment. But only non-invasive and well-tested elements should be backported.

- RC1 beginning of next week

- Bug squashing effort during the two weeks that follow.

- RC2 around June 15th.

- Another week of bug squashing, if necessary.

- Release of 6.4.4 by end of June, the latest.

That sound ok ?

Moritz

martinl · May 26, 2014, 11:09am

Hi,

···

2014-05-26 12:58 GMT+02:00 Moritz Lennert <mlennert@club.worldonline.be>:

I think we are not far at all from releasing, so maybe something like this:

Real freeze of grass64_release at the end of this week. This means that any backports from grass6_devel should happen before that moment. But only non-invasive and well-tested elements should be backported.

RC1 beginning of next week

Bug squashing effort during the two weeks that follow.

RC2 around June 15th.

Another week of bug squashing, if necessary.

Release of 6.4.4 by end of June, the latest.

That sound ok ?

sounds good to me… Martin

–
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

neteler · May 31, 2014, 9:19pm

On Mon, May 26, 2014 at 12:58 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...

- Real freeze of grass64_release at the end of this week. This means that
any backports from grass6_devel should happen before that moment. But only
non-invasive and well-tested elements should be backported.

Seems nothing got backported in the past week any more:
http://trac.osgeo.org/grass/log/grass/branches/releasebranch_6_4

- RC1 beginning of next week

Should that happen then?

Markus

mlennert · June 2, 2014, 8:41am

On 31/05/14 23:19, Markus Neteler wrote:

On Mon, May 26, 2014 at 12:58 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...

- Real freeze of grass64_release at the end of this week. This means that
any backports from grass6_devel should happen before that moment. But only
non-invasive and well-tested elements should be backported.

Seems nothing got backported in the past week any more:
http://trac.osgeo.org/grass/log/grass/branches/releasebranch_6_4

At the same time, we did not officially announce the calendar (it was in a reply to a long-going thread...). But let's hope all the interested people saw the calendar.

- RC1 beginning of next week

Should that happen then?

I think (also in line with the above) a clear freeze announcement has to go out first to give a 24-48h warning to everyone. Then RC1 can be tagged.

Sorry, but I won't be of much help these days as we've started exams here and I'll be busy with that almost all week.

Moritz

neteler · June 2, 2014, 11:54am

On Mon, Jun 2, 2014 at 10:41 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:

On 31/05/14 23:19, Markus Neteler wrote:

On Mon, May 26, 2014 at 12:58 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...

- Real freeze of grass64_release at the end of this week. This means that
any backports from grass6_devel should happen before that moment. But
only
non-invasive and well-tested elements should be backported.

Seems nothing got backported in the past week any more:
http://trac.osgeo.org/grass/log/grass/branches/releasebranch_6_4

At the same time, we did not officially announce the calendar (it was in a
reply to a long-going thread...). But let's hope all the interested people
saw the calendar.

Yes.

- RC1 beginning of next week

Should that happen then?

I think (also in line with the above) a clear freeze announcement has to go
out first to give a 24-48h warning to everyone. Then RC1 can be tagged.

Sorry, but I won't be of much help these days as we've started exams here
and I'll be busy with that almost all week.

So I'll wait...

cheers
Markus

neteler · June 5, 2014, 7:56am

hi all,

I would be able to tag RC1 tomorrow (Friday) if there are no objections.

Are there any pending backports? I have some uncommitted fixes for
r.pack and v.external but will not commit them to avoid another
flamewar.

Markus

martinl · June 5, 2014, 2:46pm

Hi Markus,

2014-06-05 9:56 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

I would be able to tag RC1 tomorrow (Friday) if there are no objections.

Are there any pending backports? I have some uncommitted fixes for
r.pack and v.external but will not commit them to avoid another
flamewar.

no objection for my side. From other project (GDAL for example) I got
feeling that RC period must be short. So e.g. RC2 or final one/two
weeks after RC1.... Also reporting bunch of blockers during RC stage
can be interpreted as attempt to block release. I hope that for GRASS
7 will defined fixed time-based release policy with freeze stage
(one/two months - ideal time for reporting blockers), than simply
release and go on...

Martin

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa

martinl · June 5, 2014, 7:19pm

Hi,

2014-06-05 17:47 GMT+02:00 Moritz Lennert <moritz.lennert@ulb.ac.be>:

[...]

As I've already told Markus off-list, I think that in order for this to work
we would need a clearly defined release-process with clear announcements of
the different steps (pre-freeze warning sufficiently early, freeze
announcement, pre-tag announcement, etc) and a strict respect of the rules
during this process (i.e. no non bugfix commits during a freeze), etc.

I'm not convinced that a time-based release-policy is the solution, but I
think a more clearly defined release-process policy might help in avoiding
frustrations.

right, let's push out 6.4.4 somehow, new release policy is question for G7...

Martin

--
Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa