[GRASS5] New GIS Manager

Radim Blazek radim.blazek at gmail.com
Mon Mar 27 03:34:31 EST 2006


On 3/27/06, Markus Neteler <neteler at itc.it> wrote:
> My opinion is to not backport it but to use the available energy to prepare
> a GRASS 6.1.0 release. Only then it can enter Debian etc.
>
> Maybe people could indicate how far they see their contributions in terms
> of sort-of-stability to create a release branch? I am not talking about
> 6.2.-stable,
> just a somewhat reliable 6.1.0 release to illustrate the great new features
> of 6.1.

I agree that we should start 6.2 release process soon. I would prefer however
to avoid to have 6.2 branch for a long time before 6.2.0 release.
Because we have usually problems to keep in sync bug fixes in more branches
as many occasional contributors do not follow the release process
or forget to commit bug fixes into both branches.

My suggestion is to prepare 6.2.0 release in HEAD and create the 6.2
branch in the moment of 6.2.0 release. In the perion 6.2 feature freeze
- 6.2.0 release all contributors should concentrate on bug fixing.

What features are missing for 6.2 feature freeze? GEM,... ?

Radim




More information about the grass-dev mailing list