Because of the code freeze in December (or January?), a number of change I made to the GIS Manager prior to the release of 6.0 didn’t make it into 6.0. However, they are in 6.1 (e.g., buttons to manage monitors). Will these go into 6.0.1 or will they remain relegated to 6.1?
Michael
C. Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
PO Box 872402
Arizona State University
Tempe, AZ 85287-2402
USA
Because of the code freeze in December (or January?), a number of
change I made to the GIS Manager prior to the release of 6.0 didn¹t
make it into 6.0. However, they are in 6.1 (e.g., buttons to manage
monitors). Will these go into 6.0.1 or will they remain relegated to
6.1?
6.0.1 is for bug fixes only, not for new features. So the usability
improvements stay in the 6.1 branch. This improves stability in the
release branch by stopping new features from introducing new bugs
(unnoticed side effects).
e.g. "GRASS does not compile with gcc 4.0" is a critical fix. "Nicer
font rendering for d.paint.labels" isn't.
On Mon, Jul 04, 2005 at 04:47:39PM +1200, Hamish wrote:
> Because of the code freeze in December (or January?), a number of
> change I made to the GIS Manager prior to the release of 6.0 didn¹t
> make it into 6.0. However, they are in 6.1 (e.g., buttons to manage
> monitors). Will these go into 6.0.1 or will they remain relegated to
> 6.1?
6.0.1 is for bug fixes only, not for new features. So the usability
improvements stay in the 6.1 branch. This improves stability in the
release branch by stopping new features from introducing new bugs
(unnoticed side effects).
e.g. "GRASS does not compile with gcc 4.0" is a critical fix.
Is it really critical for 6.0.1? Which distro comes with gcc4?
Since it's half done only for 6.1, I suggest to postpone it
for 6.0.2 so that we have time for testing.
On Jul 4, 2005, at 11:02 AM, Markus Neteler wrote:
e.g. "GRASS does not compile with gcc 4.0" is a critical fix.
Is it really critical for 6.0.1? Which distro comes with gcc4?
Since it's half done only for 6.1, I suggest to postpone it
for 6.0.2 so that we have time for testing.
er, Mac OS 10.4 (Tiger) does. But really the only problem with GCC 4 there is r.terraflow (which sounds like that half-done part).
There is a theory which states that if ever anyone discovers exactly what the universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarrely inexplicable. There is another theory which states that this has already happened.
-Hitchhiker's Guide to the Galaxy 2nd season intro
At 18:02, lunedì 04 luglio 2005, Markus Neteler has probably written:
> e.g. "GRASS does not compile with gcc 4.0" is a critical fix.
Is it really critical for 6.0.1? Which distro comes with gcc4?
Since it's half done only for 6.1, I suggest to postpone it
for 6.0.2 so that we have time for testing.
Well, I still think that it is a good idea to get the current
code published. Changes for gcc4 are quite intrusive (correct me
if I am wrong), are not yet finished, not tested completely etc.
There is a possibility to publish 6.0.2 for that.
However, if the majority prefers to wait, then we can do that
of course. Sorry then for the people using 6.0.0...
Markus
At 18:02, lunedì 04 luglio 2005, Markus Neteler has probably written:
> > e.g. "GRASS does not compile with gcc 4.0" is a critical fix.
>
> Is it really critical for 6.0.1? Which distro comes with gcc4?
> Since it's half done only for 6.1, I suggest to postpone it
> for 6.0.2 so that we have time for testing.
>
> Let's not wait with 6.0.1 release.
--
Paolo Cavallini
cavallini@faunalia.it www.faunalia.it www.faunalia.com
Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy Tel: (+39)348-3801953
--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy
> > > e.g. "GRASS does not compile with gcc 4.0" is a critical fix.
> >
> > Is it really critical for 6.0.1? Which distro comes with gcc4?
> > Since it's half done only for 6.1, I suggest to postpone it
> > for 6.0.2 so that we have time for testing.
AKAIK:
Fedora Core 4, MacOSX 10.4; Debian's development branches, but they are
currently undergoing a lot of change so I think we can get away without
supporting them for a little while. It's easy enough to patch 6.0.1 with
the existing gcc4 fixes and let any problems get sorted out in the
DebianGIS repository before committing to Debian/unstable; and if that
goes smoothly look at putting them in the GRASS 6.0 release branch.
(use testing for testing and release branches for stable code after all)
Debian has a gcc-3.4 package that can be installed along side a default
install of gcc-4.0 too.....
Well, I still think that it is a good idea to get the current
code published. Changes for gcc4 are quite intrusive (correct me
if I am wrong), are not yet finished, not tested completely etc.
There is a possibility to publish 6.0.2 for that.
Although I don't have any experience with them, the gcc4 fixes are
indeed new and lightly tested.
So there remain several bugs in various places that we don't like in
6.0.1, but I agree there is no strong reason to wait. As you say, there
can always be a 6.0.2. In fact I think we should certainly keep the
6.0.x line alive for a while and there should one-day be a 6.0.3 and
even .4 -- give you something stable to write a 3rd ed. book on e.g.
If d.where is giving wrong results, I do hope we can fix that before
we get to 6.0.1-final ... Segfaulting etc is an inconvenience, but
silently reporting the wrong answer is very bad.
On the other side, should we plan on gcc4 support for 5.4.1? --As 5.4.1
might be the last of the GRASS 5's? Depends on how serious the imagery
lib changes are I guess.
Note that refers to gcc version 3.3.5 (Debian 1:3.3.5-13), the same
version as in Debian/Stable (Sarge); not gcc 4. I expect Debian/
unstable->testing will be using gcc 4.0 in the near future though.
On Tue, Jul 05, 2005 at 04:30:48PM +1200, Hamish wrote:
> > > > e.g. "GRASS does not compile with gcc 4.0" is a critical fix.
> > >
> > > Is it really critical for 6.0.1? Which distro comes with gcc4?
> > > Since it's half done only for 6.1, I suggest to postpone it
> > > for 6.0.2 so that we have time for testing.
AKAIK:
Fedora Core 4, MacOSX 10.4; Debian's development branches, but they are
currently undergoing a lot of change so I think we can get away without
supporting them for a little while.
Ok, but today a major part of the users will still use Fedora Core 3
and MacOSX 10.3. Releasing 6.0.1 now helps for all these users
(also Mandriva, Windows etc pp).
etc. I guess I don't have to repeat
It's easy enough to patch 6.0.1 with
the existing gcc4 fixes and let any problems get sorted out in the
DebianGIS repository before committing to Debian/unstable; and if that
goes smoothly look at putting them in the GRASS 6.0 release branch.
(use testing for testing and release branches for stable code after all)
Debian has a gcc-3.4 package that can be installed along side a default
install of gcc-4.0 too.....
> Well, I still think that it is a good idea to get the current
> code published. Changes for gcc4 are quite intrusive (correct me
> if I am wrong), are not yet finished, not tested completely etc.
> There is a possibility to publish 6.0.2 for that.
Although I don't have any experience with them, the gcc4 fixes are
indeed new and lightly tested.
I think Brad is doing a great job. But even he says that things are
not complete yet.
So there remain several bugs in various places that we don't like in
6.0.1, but I agree there is no strong reason to wait. As you say, there
can always be a 6.0.2. In fact I think we should certainly keep the
6.0.x line alive for a while and there should one-day be a 6.0.3 and
even .4 -- give you something stable to write a 3rd ed. book on e.g.
We are thinking about it
If d.where is giving wrong results, I do hope we can fix that before
we get to 6.0.1-final ... Segfaulting etc is an inconvenience, but
silently reporting the wrong answer is very bad.
I agree.
On the other side, should we plan on gcc4 support for 5.4.1? --As 5.4.1
might be the last of the GRASS 5's? Depends on how serious the imagery
lib changes are I guess.
