[GRASS5] 5.0.0 branch started...

GRASS GRASS developer
1

Hi all,

(oops, I did it again)
the branching has been started. This means:

- please don't submit to the exp/head
- only fixes should go into this branch, no experiments
- please read the instructions :slight_smile:
  documents/release_rules.txt

As most of us are not yet familiar with branches, we all
have to learn.

The new branch name is:
releasebranch_11_april_2001_5_0_0

# The branch can be checked out with
#
# cvs -z3 checkout -r releasebranch_11_april_2001_5_0_0 grass

I hope I tagged it correctly (to verify, see tools/cvsbranch.sh).

What to do now:
- heavy testing of the branch is needed (all platforms)
- eventual bugs are to be fixed
- publish it asap!
- merge the fixes back into exp/head tree, close the branch
- start 5.1

Timeline: One (or two) weeks for the stable release?

Regards

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

2

On Wed, Apr 11, 2001 at 04:57:06PM +0100, Markus Neteler wrote:

- please don't submit to the exp/head

You mean: Do not submit bug-fixes to the exp/head, right?

- heavy testing of the branch is needed (all platforms)
- eventual bugs are to be fixed
- publish it asap!

As a beta or prerelease?

- merge the fixes back into exp/head tree, close the branch

We should not really close the branch.

Timeline: One (or two) weeks for the stable release?

You need a date for the beta release, one week from here.
Then we need another date for the actual 5.0.0 release.
Another four weeks.

Please include: Everybody who does not find bugs in the beta
cannot complain about them being in 5.0.0..

  Bernhard

--
Professional Service around Free Software (intevation.net)
The FreeGIS Project (freegis.org)
Association for a Free Informational Infrastructure (ffii.org)
FSF Europe (fsfeurope.org)

3

On Wed, Apr 11, 2001 at 05:35:28PM +0200, Bernhard Reiter wrote:

On Wed, Apr 11, 2001 at 04:57:06PM +0100, Markus Neteler wrote:
> - please don't submit to the exp/head

You mean: Do not submit bug-fixes to the exp/head, right?

Yes, submit to the branch instead. Later we merge them back.
Focus is on this releasebranch only at time (otherwise we
never finish that stable release).

Or, dear CVS professionals: Shall bugfixes immediately merged back?

> - heavy testing of the branch is needed (all platforms)
> - eventual bugs are to be fixed
> - publish it asap!

As a beta or prerelease?

Prerelease. pre-stable to a limited audience (our testers)

> - merge the fixes back into exp/head tree, close the branch

We should not really close the branch.

Maybe. We can discuss this later in detail.

> Timeline: One (or two) weeks for the stable release?

You need a date for the beta release, one week from here.

You are right, I was not very clear. My suggestion:

18th April: publish the branch as "pre1-stable"

Then we need another date for the actual 5.0.0 release.
Another four weeks.

That would be:
9th May for definite stable publish date.

Please include: Everybody who does not find bugs in the beta
cannot complain about them being in 5.0.0..

Mhh, finding doesn't mean having them fixed. Perhaps we'll have to
live with a few bugs, otherwise we never reach something called
"stable".

Let's see.

Happy testing,

Markus

PS: I have fixed a compile bug in src/mapdev/v.in.atlas/isle.c
    and applied to the branch. Seems to become the first branch/exp
    lesson. Shall I fix in exp as well?

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'