Hello everyone,
Updating from SVN this morning I see that the version number is now 6.4.svn - I'm not sure if that's right? I thought it should be 6.3.svn until a release branch for 6.4 is created, and the version number on that branch will be 6.4.svn. At that point the version on develbranch_6, which will be in operation by then, will become 6.5.svn (although there might not ever be any 6.5 releases, similar to 5.5).
It is all a bit confusing though since we've started partially abandoning the odd-development/stable-release system.
Any thoughts?
2008/4/24, Paul Kelly <paul-grass@stjohnspoint.co.uk>:
Updating from SVN this morning I see that the version number is now 6.4.svn
- I'm not sure if that's right? I thought it should be 6.3.svn until a
release branch for 6.4 is created, and the version number on that branch
will be 6.4.svn. At that point the version on develbranch_6, which will be
in operation by then, will become 6.5.svn (although there might not ever be
any 6.5 releases, similar to 5.5).
Since 6.3.0 is out we can create 'develbranch_6' branch, e.g. during
this weekend (as 6.4svn). After creating 'releasebranch_6_4' (as
6.4svn) it can be renamed to 6.5svn. Trunk becomes 7.0svn. Does it
make sense to you?
Martin
It is all a bit confusing though since we've started partially abandoning
the odd-development/stable-release system.
Any thoughts?
2008/4/24, Paul Kelly <paul-grass@stjohnspoint.co.uk>:
Updating from SVN this morning I see that the version number is now 6.4.svn
- I'm not sure if that's right? I thought it should be 6.3.svn until a
release branch for 6.4 is created, and the version number on that branch
will be 6.4.svn. At that point the version on develbranch_6, which will be
in operation by then, will become 6.5.svn (although there might not ever be
any 6.5 releases, similar to 5.5).
Since 6.3.0 is out we can create 'develbranch_6' branch, e.g. during
this weekend (as 6.4svn).
It's not a big deal but why not save the 6.4-svn numbering for the 6.4 release branch was what I was asking.
After creating 'releasebranch_6_4' (as
6.4svn) it can be renamed to 6.5svn. Trunk becomes 7.0svn. Does it
make sense to you?
On Thu, Apr 24, 2008 at 12:11 PM, Paul Kelly
<paul-grass@stjohnspoint.co.uk> wrote:
Hello everyone,
Updating from SVN this morning I see that the version number is now 6.4.svn
- I'm not sure if that's right? I thought it should be 6.3.svn until a
release branch for 6.4 is created, and the version number on that branch
will be 6.4.svn. At that point the version on develbranch_6, which will be
in operation by then, will become 6.5.svn (although there might not ever be
any 6.5 releases, similar to 5.5).
It is all a bit confusing though since we've started partially abandoning
the odd-development/stable-release system.
that's not intended.
Obviously, trunk needs to be changes to 7.0.svn.
We should fork the 6.4 now, called "develbranch_6". From that,
in future, "releasebranch_6_4" will be forked.
AFAIK there is some SVN switch magic so that you can just update locally
without downloading all again.
On Thu, Apr 24, 2008 at 12:11 PM, Paul Kelly
<paul-grass@stjohnspoint.co.uk> wrote:
Hello everyone,
Updating from SVN this morning I see that the version number is now 6.4.svn
- I'm not sure if that's right? I thought it should be 6.3.svn until a
release branch for 6.4 is created, and the version number on that branch
will be 6.4.svn. At that point the version on develbranch_6, which will be
in operation by then, will become 6.5.svn (although there might not ever be
any 6.5 releases, similar to 5.5).
It is all a bit confusing though since we've started partially abandoning
the odd-development/stable-release system.
Updating from SVN this morning I see that the version number is now
6.4.svn - I'm not sure if that's right? I thought it should be 6.3.svn
until a release branch for 6.4 is created, and the version number on
that branch will be 6.4.svn. At that point the version on
develbranch_6,
which will be in operation by then, will become 6.5.svn (although there
might not ever be any 6.5 releases, similar to 5.5).
Martin:
Since 6.3.0 is out we can create 'develbranch_6' branch, e.g. during
this weekend (as 6.4svn). After creating 'releasebranch_6_4' (as
6.4svn) it can be renamed to 6.5svn.
I would wait until 6.4 feature freeze before branching off a
releasebranch_6_4 and setting the version to 6.5.svn. Otherwise there is
lots of backporting and double handling to do. Especially with whatever
GRASS 7(trunk) fore-porting there is to be done.
or is the time right to declare GRASS 6 feature-frozen for all but wx and
winGRASS development?
Perhaps wait a week or two anyway before branching off _6_4 from _6, to
let us finish with 6.3.0 business and catch up to our thoughts.
It is all a bit confusing though since we've started partially
abandoning the odd-development/stable-release system.
AFAIK we haven't abandoned that at all. It's just that we happened to
make 6.3.0 a really nice and usable beta since no new features [well,
few] have gone into the stable branch since 6.2 was branched off HEAD in
August 2006.
-or-
I see no reason to abandon that. Both odd and even numbers are free and
it gives us some room to play with semi-stable releases like 6.3.0.
> Since 6.3.0 is out we can create 'develbranch_6' branch, e.g. during
> this weekend (as 6.4svn). After creating 'releasebranch_6_4' (as
> 6.4svn) it can be renamed to 6.5svn.
I would wait until 6.4 feature freeze before branching off a
releasebranch_6_4 and setting the version to 6.5.svn. Otherwise there is
lots of backporting and double handling to do. Especially with whatever
GRASS 7(trunk) fore-porting there is to be done.
or is the time right to declare GRASS 6 feature-frozen for all but wx and
winGRASS development?
Perhaps wait a week or two anyway before branching off _6_4 from _6, to
let us finish with 6.3.0 business and catch up to our thoughts.
I agree with you, task for now is to create develbranch_6 and move
grass6 development from trunk to this branch. Release branch for 6_4
will be created later.
On Thu, Apr 24, 2008 at 3:55 PM, Martin Landa <landa.martin@gmail.com> wrote:
I agree with you, task for now is to create develbranch_6 and move
grass6 development from trunk to this branch.
Release branch for 6_4 will be created later.
Any objections to follow this plan?
Then we can rename trunk to 7.0.svn which resolves Paul's problem and
finally opens the door for GRASS 7 development.
> Obviously, trunk needs to be changes to 7.0.svn.
>
> We should fork the 6.4 now, called "develbranch_6". From that,
> in future, "releasebranch_6_4" will be forked.
I just don't understand why the change to 6.4 numbering now - I thought
there might have been more 6.3 versions before we create the release
branch.
Now that 6.3.0 is "released", 6.3.x = "stable", 6.4.x = "unstable", so
6.3 = release branch, 6.4 = trunk (soon to become development branch
so that 7.x = trunk).
