Now that the gis.m startup error message problem is (fingers crossed)
dealt with, are there any other outstanding issues holding back a 6.2.1
release? These should be critical bug fixes only.
Due to badly broken ps.map in 6.2.0 and the common hard to understand
gis.m startup error message, I'd hope for a release soon. It is now 30
days since 6.2.0 was released (and that's a nice round number).
* For NVIZ bug #4725 I have added a warning message with suggested
work-around so don't consider that release critical (it may take some
time to fix this one).
* I don't know anything about the r.distance NULL bugfix, do can't
comment on that.
Markus: can you trigger an new 6.2-releasebranch snapshot for testing?
Hamish
ps - any cvs2cl.pl hints?
Do you need to do a full checkout of the 6.2 branch to run it?
Are the following requests->commands correct?
doc/howto_release.txt: #create ChangeLog on release branch:
sh tools/cvs2cl.pl --follow "$CVSBRANCH"
6.2.newbranch->6.2.latest
-F *BRANCH*, --follow *BRANCH*
Show only revisions on or ancestral to *BRANCH*.
or
6.2.a -> 6.2.b
--delta *FROM_TAG*:*TO_TAG*
Attempt a delta between two tags (since *FROM_TAG* up to and
including *TO_TAG*). The algorithm is a simple date-based one
(this is a hard problem) so results are imperfect.
On Thu, Nov 30, 2006 at 08:24:14PM +1300, Hamish wrote:
Hi.
Now that the gis.m startup error message problem is (fingers crossed)
dealt with, are there any other outstanding issues holding back a 6.2.1
release? These should be critical bug fixes only.
Due to badly broken ps.map in 6.2.0 and the common hard to understand
gis.m startup error message, I'd hope for a release soon. It is now 30
days since 6.2.0 was released (and that's a nice round number).
* For NVIZ bug #4725 I have added a warning message with suggested
work-around so don't consider that release critical (it may take some
time to fix this one).
* I don't know anything about the r.distance NULL bugfix, do can't
comment on that.
Markus: can you trigger an new 6.2-releasebranch snapshot for testing?
Yes, I was thinking the same recently.
I will prepare a testing candidate.
ps - any cvs2cl.pl hints?
Do you need to do a full checkout of the 6.2 branch to run it?
Yes, I guess so.
Are the following requests->commands correct?
doc/howto_release.txt: #create ChangeLog on release branch:
sh tools/cvs2cl.pl --follow "$CVSBRANCH"
This worked so far.
6.2.newbranch->6.2.latest
-F *BRANCH*, --follow *BRANCH*
Show only revisions on or ancestral to *BRANCH*.
or
6.2.a -> 6.2.b
--delta *FROM_TAG*:*TO_TAG*
Attempt a delta between two tags (since *FROM_TAG* up to and
including *TO_TAG*). The algorithm is a simple date-based one
(this is a hard problem) so results are imperfect.
For the latter two I don't know, someone may suggest.
Would be nice to publish the delta, too.
On 11/30/06 12:24 AM, "Hamish" <hamish_nospam@yahoo.com> wrote:
Now that the gis.m startup error message problem is (fingers crossed)
dealt with, are there any other outstanding issues holding back a 6.2.1
release? These should be critical bug fixes only.
Due to badly broken ps.map in 6.2.0 and the common hard to understand
gis.m startup error message, I'd hope for a release soon. It is now 30
days since 6.2.0 was released (and that's a nice round number).
As far as I know, we're pretty stable. OK from my perspective. I've only
been breaking NVIZ for 6.3
Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University
