[GRASS5] Fertilizer 2002: CVS and release strategies

[Bernhard Reiter]

On Sun, Jan 20, 2002 at 02:03:44AM +0000, Glynn Clements wrote:
> Bernhard Reiter wrote:
> 
> > * Each change commited to the release branch must be immediately
> >    commited to the main branch. If change in stable branch was
> >    not commited to development branch, developer will be asked to do that
> >    via mailing list.
> 
> This isn't always as straightforward as the preceding paragraph
> implies.

True.
Still, if you fix a release critical bug on the _release_ branch
you should make sure that the bug is fixed in the _main_ branch.
This might be a different fix, though.


> If someone has been modifying the corresponding program/library on the
> development branch (trunk), 

Please call it "main" branch, as it might be confused with the 
"development" tree to easily otherwise.

> a fix which works for the stable version
> may not work on (or even apply to) the development version. 

The release branch should never be far away from the main branch
on the stable tree.


> If the
> development version has changed significantly and/or is in a state of
> flux, someone who can produce a fix for the stable version might not
> be able to determine a suitable fix for the development version.

It has to be tried, though.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 248 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20020120/593700c9/attachment.bin