[GRASS-dev] grass6.3.0RC5 preparation

GRASS GIS GRASS GIS developer
1

Hi,

today I copied wxPython GUI code and g.gui module to releasebranch_63,
related changesets:

http://trac.osgeo.org/grass/changeset/30184
http://trac.osgeo.org/grass/changeset/30185
http://trac.osgeo.org/grass/changeset/30186
http://trac.osgeo.org/grass/changeset/30190
http://trac.osgeo.org/grass/changeset/30191

Please test it out if you can.

grass63 -wxpython
...

I hope we would be able to release RC5 let's say on Monday. I also
created initial version of release-news page for RC5

http://trac.osgeo.org/grass/wiki/Release/6.3.0RC5-News

I have a couple questions here, just to be sure

1) I copied announcement text from the previous release-news page
(RC4) and I made some minor improvements in text (note wxPython,
etc.). Anyway this text is missing in rc3-rc1 release-news pages. I
guess should be included in all release-new pages including RC's.

2) List of changes, the list reflects only changes made from the last
release candidate (so rc2 reflects rc2-rc1, rc3:r3-r2, rc4:r4-r3).
Shouldn't be the list accumulative? I mean rc2:rc2-rc1, rc3:rc3-rc1,
rc4:rc4-rc1, rc5-rc5-rc1.

Best regards, Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

2

Hi,

sorry I forgot to mention..

2008/2/16, Martin Landa <landa.martin@gmail.com>:

today I copied wxPython GUI code and g.gui module to releasebranch_63,
related changesets:

http://trac.osgeo.org/grass/changeset/30184
http://trac.osgeo.org/grass/changeset/30185
http://trac.osgeo.org/grass/changeset/30186
http://trac.osgeo.org/grass/changeset/30190
http://trac.osgeo.org/grass/changeset/30191

I haven't backported changes in configure script [1] since there are
problems on Mandriva (I guess not only here) [2]. Maybe configure
script could be merged from trunk now and later (before 6.3.0) fixed?
I have tested that till now only on Debian.

1) I copied announcement text from the previous release-news page
(RC4) and I made some minor improvements in text (note wxPython,
etc.). Anyway this text is missing in rc3-rc1 release-news pages. I
guess should be included in all release-new pages including RC's.

2) List of changes, the list reflects only changes made from the last
release candidate (so rc2 reflects rc2-rc1, rc3:r3-r2, rc4:r4-r3).
Shouldn't be the list accumulative? I mean rc2:rc2-rc1, rc3:rc3-rc1,
rc4:rc4-rc1, rc5-rc5-rc1.

3) There are milestones for rc1:rc3, but not for rc4.

http://trac.osgeo.org/grass/milestone/6.3.0RC3

I think milestone for 6.3.0 would be enough here, milestones for each
RC are not necessary I think and maybe confusing when reporting the
new ticket?

Martin

[1] http://trac.osgeo.org/grass/ticket/38
[2] http://trac.osgeo.org/grass/ticket/51

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

3

Martin Landa wrote:

I also created initial version of release-news page for RC5
http://trac.osgeo.org/grass/wiki/Release/6.3.0RC5-News

I have a couple questions here, just to be sure

1) I copied announcement text from the previous release-news page
(RC4) and I made some minor improvements in text (note wxPython,
etc.). Anyway this text is missing in rc3-rc1 release-news pages. I
guess should be included in all release-new pages including RC's.

eh? what text was missing? about wx?

2) List of changes, the list reflects only changes made from the last
release candidate (so rc2 reflects rc2-rc1, rc3:r3-r2, rc4:r4-r3).
Shouldn't be the list accumulative? I mean rc2:rc2-rc1, rc3:rc3-rc1,
rc4:rc4-rc1, rc5-rc5-rc1.

For RC announcements I'd just list major changes since the last RC in
bullet points. For the final release we should try and list major new
features since 6.2.
see http://article.gmane.org/gmane.comp.gis.grass.devel/24802/

For more detail tools/cvs2cl.pl (or svn equivalent) can produce the
changelog back to 6.3.0 branch creation, and before that date from the
point 6.2.0 branched away from HEAD. see:
  http://grass.gdf-hannover.de/wiki/GRASS_6.2_Feature_Plan#TODO
In the past the release manager put the Changelog in the release
..tar.gz and the shorter inter-release changelog was posted to the
website after that.

3) There are milestones for rc1:rc3, but not for rc4.
http://trac.osgeo.org/grass/milestone/6.3.0RC3
I think milestone for 6.3.0 would be enough here, milestones for each
RC are not necessary I think and maybe confusing when reporting the
new ticket?

I agree, just one milestone for 6.3.0 is enough.

Remember the old milestone "tracker":
http://grass.gdf-hannover.de/wiki/GRASS_6.3_Feature_Plan#Must_do

Hamish

      ____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

4

Hi,

2008/2/17, Hamish <hamish_b@yahoo.com>:

Martin Landa wrote:
> I also created initial version of release-news page for RC5
> http://trac.osgeo.org/grass/wiki/Release/6.3.0RC5-News
>
> I have a couple questions here, just to be sure
>
> 1) I copied announcement text from the previous release-news page
> (RC4) and I made some minor improvements in text (note wxPython,
> etc.). Anyway this text is missing in rc3-rc1 release-news pages. I
> guess should be included in all release-new pages including RC's.

Hamish:

eh? what text was missing? about wx?

compare

http://trac.osgeo.org/grass/wiki/Release/6.3.0RC4-News

and

http://trac.osgeo.org/grass/wiki/Release/6.3.0RC3-News

> 2) List of changes, the list reflects only changes made from the last
> release candidate (so rc2 reflects rc2-rc1, rc3:r3-r2, rc4:r4-r3).
> Shouldn't be the list accumulative? I mean rc2:rc2-rc1, rc3:rc3-rc1,
> rc4:rc4-rc1, rc5-rc5-rc1.

For RC announcements I'd just list major changes since the last RC in
bullet points. For the final release we should try and list major new
features since 6.2.
see http://article.gmane.org/gmane.comp.gis.grass.devel/24802/

For more detail tools/cvs2cl.pl (or svn equivalent) can produce the
changelog back to 6.3.0 branch creation, and before that date from the
point 6.2.0 branched away from HEAD. see:
  http://grass.gdf-hannover.de/wiki/GRASS_6.2_Feature_Plan#TODO
In the past the release manager put the Changelog in the release
..tar.gz and the shorter inter-release changelog was posted to the
website after that.

> 3) There are milestones for rc1:rc3, but not for rc4.
> http://trac.osgeo.org/grass/milestone/6.3.0RC3
> I think milestone for 6.3.0 would be enough here, milestones for each
> RC are not necessary I think and maybe confusing when reporting the
> new ticket?

I agree, just one milestone for 6.3.0 is enough.

OK, I will modify rc3-rc1 to reflect 6.3.0 as the milestone.

Remember the old milestone "tracker":
http://grass.gdf-hannover.de/wiki/GRASS_6.3_Feature_Plan#Must_do

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *