concerning the 6.0.0beta1 release, please note that
developers simply continue in the existing repository
(cvs up -dP as usual).
However, keep in mind the rules:
http://grass.itc.it/pipermail/grass5/2004-December/016793.html
"Code freeze starts with grass_6_0_0_beta_1, that means no new features
and improvements to existing content of grass51 CVS, only bugfixes may
be submitted. This includes also build system and messages in C code.
If you want to add new features, you have to do that before January 5 2005.
[ok, yesterday due to postponed publication]
In grass_6_0_0_beta_1 and grass_6_0_0_beta_2 it is however allowed to
add new modules.
New translations in /grass51/locale and HTML descriptions
(description.html) can be added or modified during grass_6_0_0_beta_1 -
grass_6_0_0_beta_3.
"
---------
(also @Bernhard):
Let me suggest to change the CVS repository name from grass51/
to something more general. Should be a simple 'mv' in the CVS repository
or, easier, just a link.
On Wed, Jan 12, 2005 at 07:07:34PM +0100, Markus Neteler wrote:
(also @Bernhard):
Let me suggest to change the CVS repository name from grass51/
to something more general. Should be a simple 'mv' in the CVS repository
or, easier, just a link.
What would you suggest for a name?
As developers have checked out the stuff under this repository,
we might as well keep it for historical value.
Otherwise people might need to recheckout, change all CVS/Repository names
and check all links and scripts we have pointing there.
On Thu, Jan 13, 2005 at 07:25:46PM +0100, Bernhard Reiter wrote:
On Wed, Jan 12, 2005 at 07:07:34PM +0100, Markus Neteler wrote:
> (also @Bernhard):
> Let me suggest to change the CVS repository name from grass51/
> to something more general. Should be a simple 'mv' in the CVS repository
> or, easier, just a link.
What would you suggest for a name?
for example
- gnugrass
- grass
- grassgis
- grass6
As developers have checked out the stuff under this repository,
we might as well keep it for historical value.
Otherwise people might need to recheckout, change all CVS/Repository names
and check all links and scripts we have pointing there.
That's why I suggested a link.
e.g., in CVS:
mv grass51/ grass6/
ln -s grass6 grass51
should work.
IMHO it's pretty confusing that we have 5.3, 5.4 and the
6.0 code living in grass51/.
On Thu, Jan 13, 2005 at 07:25:46PM +0100, Bernhard Reiter wrote:
On Wed, Jan 12, 2005 at 07:07:34PM +0100, Markus Neteler wrote:
(also @Bernhard):
Let me suggest to change the CVS repository name from grass51/
to something more general. Should be a simple 'mv' in the CVS repository
or, easier, just a link.
What would you suggest for a name?
for example
- gnugrass
- grass
- grassgis
- grass6
'gnugrass' certainly not, there is no relation to gnu.
On Fri, Jan 14, 2005 at 01:36:16PM +0100, Markus Neteler wrote:
On Thu, Jan 13, 2005 at 07:25:46PM +0100, Bernhard Reiter wrote:
> On Wed, Jan 12, 2005 at 07:07:34PM +0100, Markus Neteler wrote:
> > (also @Bernhard):
> > Let me suggest to change the CVS repository name from grass51/
> > to something more general. Should be a simple 'mv' in the CVS repository
> > or, easier, just a link.
>
> What would you suggest for a name?
for example
- gnugrass
- grass
- grassgis
- grass6
> As developers have checked out the stuff under this repository,
> we might as well keep it for historical value.
> Otherwise people might need to recheckout, change all CVS/Repository names
> and check all links and scripts we have pointing there.
That's why I suggested a link.
e.g., in CVS:
mv grass51/ grass6/
ln -s grass6 grass51
should work.
I can try.
When shall I do this?
(I need to stop CVS access for a period.
IMHO it's pretty confusing that we have 5.3, 5.4 and the
6.0 code living in grass51/.
Nah, I'd say developers can handle it.
And in some time in the future we might offer grass development
a subversion or monotone server for development here at Intevation.
I just don't know when exactely.
On 1/19/05 7:43 AM, "Bernhard Reiter" <bernhard@intevation.de> wrote:
On Fri, Jan 14, 2005 at 01:36:16PM +0100, Markus Neteler wrote:
On Thu, Jan 13, 2005 at 07:25:46PM +0100, Bernhard Reiter wrote:
On Wed, Jan 12, 2005 at 07:07:34PM +0100, Markus Neteler wrote:
(also @Bernhard):
Let me suggest to change the CVS repository name from grass51/
to something more general. Should be a simple 'mv' in the CVS repository
or, easier, just a link.
What would you suggest for a name?
for example
- gnugrass
- grass
- grassgis
- grass6
As developers have checked out the stuff under this repository,
we might as well keep it for historical value.
Otherwise people might need to recheckout, change all CVS/Repository names
and check all links and scripts we have pointing there.
That's why I suggested a link.
e.g., in CVS:
mv grass51/ grass6/
ln -s grass6 grass51
should work.
I can try.
When shall I do this?
(I need to stop CVS access for a period.
IMHO it's pretty confusing that we have 5.3, 5.4 and the
6.0 code living in grass51/.
Nah, I'd say developers can handle it.
And in some time in the future we might offer grass development
a subversion or monotone server for development here at Intevation.
I just don't know when exactely.
______________________________
Michael Barton, Professor of Anthropology
School of Human Evolution and Social Change
Arizona State University
Tempe, AZ 85287-2402
USA
On Wed, Jan 19, 2005 at 03:43:47PM +0100, Bernhard Reiter wrote:
On Fri, Jan 14, 2005 at 01:36:16PM +0100, Markus Neteler wrote:
Link not done yet, because my question below went unanswered so far.
If there are not objections I will then probably just go ahead
when I have a few minutes to do this.
> That's why I suggested a link.
>
> e.g., in CVS:
>
> mv grass51/ grass6/
> ln -s grass6 grass51
>
> should work.
I can try.
When shall I do this?
(I need to stop CVS access for a period.
On Wed, Feb 02, 2005 at 06:26:06PM +0100, Bernhard Reiter wrote:
On Wed, Jan 19, 2005 at 03:43:47PM +0100, Bernhard Reiter wrote:
> On Fri, Jan 14, 2005 at 01:36:16PM +0100, Markus Neteler wrote:
Link not done yet, because my question below went unanswered so far.
If there are not objections I will then probably just go ahead
when I have a few minutes to do this.
> > That's why I suggested a link.
> >
> > e.g., in CVS:
either:
> > mv grass51/ grass6/
or:
> > ln -s grass6 grass51
The latter is the fast and less risky one
which doesn't break nothing.
> > should work.
>
> I can try.
> When shall I do this?
> (I need to stop CVS access for a period.
It's hard to decide from here when you'll have time
If above ln -s thing works, the CVS will be unavailable for 1-5 minutes
(which may just look like a local network problem at our end).
Probably sending the mail to announce a CVS downtime takes
more time to be processed in our Mailman with currently 385 subscribers
than just doing it.
I think that we all have enough patience to wait even longer
than 5 minutes. If the link idea doesn't work, we can think again.
On Thu, Feb 03, 2005 at 11:29:14AM +0100, Markus Neteler wrote:
On Wed, Feb 02, 2005 at 06:26:06PM +0100, Bernhard Reiter wrote:
> On Wed, Jan 19, 2005 at 03:43:47PM +0100, Bernhard Reiter wrote:
> > On Fri, Jan 14, 2005 at 01:36:16PM +0100, Markus Neteler wrote:
>
> Link not done yet, because my question below went unanswered so far.
> If there are not objections I will then probably just go ahead
> when I have a few minutes to do this.
>
> > > That's why I suggested a link.
> > >
> > > e.g., in CVS:
either:
> > > mv grass51/ grass6/
or:
> > > ln -s grass6 grass51
I was thinking
mv grass51 grass6
ln -s grass6 grass51
> > When shall I do this?
> > (I need to stop CVS access for a period.
It's hard to decide from here when you'll have time
This was purely asked from GRASS developer preference.
If above ln -s thing works, the CVS will be unavailable for 1-5 minutes
(which may just look like a local network problem at our end).
Commits might get interrupted, which is not advisable
if we are in high commiting mode.
