Here is the schedule for GRASS 6.0.0 release:
1) tag grass_6_0_0_beta_1 in MAIN branch (January 5 2005)
2) tag grass_6_0_0_beta_2 in MAIN branch (January 2005)
3) tag grass_6_0_0_beta_3 in MAIN branch (January/February 2005)
4) tag grass_6_0_0_beta_4 in MAIN branch (January/February 2005)
5) branch grass_6_0; tag grass_6_0_0 in grass_6_0 branch (February 2005)
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.
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.
Radim
Because of the latest bugs which were found in v.buffer and v.in.ogr
the grass_6_0_0_beta_1 is postponed.
Radim
Radim Blazek wrote:
Here is the schedule for GRASS 6.0.0 release:
1) tag grass_6_0_0_beta_1 in MAIN branch (January 5 2005)
2) tag grass_6_0_0_beta_2 in MAIN branch (January 2005)
3) tag grass_6_0_0_beta_3 in MAIN branch (January/February 2005)
4) tag grass_6_0_0_beta_4 in MAIN branch (January/February 2005)
5) branch grass_6_0; tag grass_6_0_0 in grass_6_0 branch (February 2005)
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.
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.
Radim
I want to create grass_6_0_0_beta_1 tomorrow. If you want to submit new features, please do it until tomorrow, see old messages below.
Unfortunately I have not managed to rewrite the v.buffer and I cannot reproduce the bug in v.in.ogr.
Radim
Radim Blazek wrote:
Because of the latest bugs which were found in v.buffer and v.in.ogr
the grass_6_0_0_beta_1 is postponed.
Radim
Radim Blazek wrote:
Here is the schedule for GRASS 6.0.0 release:
1) tag grass_6_0_0_beta_1 in MAIN branch (January 5 2005)
2) tag grass_6_0_0_beta_2 in MAIN branch (January 2005)
3) tag grass_6_0_0_beta_3 in MAIN branch (January/February 2005)
4) tag grass_6_0_0_beta_4 in MAIN branch (January/February 2005)
5) branch grass_6_0; tag grass_6_0_0 in grass_6_0 branch (February 2005)
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.
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.
Radim
_______________________________________________
grass5 mailing list
grass5@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass5