[GRASS5] GRASS release policy needed

[Stephan Holl]

Hello Markus, 

On Thu, 21 Jul 2005 14:05:27 +0200 Markus Neteler <neteler at itc.it>
wrote:

> Hi developers and power users,
> 
> in June I made a try to release GRASS 6.0.1:
>  http://grass.itc.it/pipermail/grass5/2005-June/018798.html
> 
> It turned out to be more complicated:
>  http://grass.itc.it/pipermail/grass5/2005-July/thread.html#18820
> 
> 
> Some observations
> 
> 1. the bugtracker is full of (old) bugs
> 2. some of the bugs are known for years, but nobody is interested/able
>    to fix them
> 3. some of the well know bugs have hold the intended release, but see
> 2. 4. While the release procedure is well documented in
> doc/howto_release.txt it is rather unclear when and under which
> conditions to release.
> 
> 
> Opinion
> 
> We should implement a better release management.
> I think that a long standing bug (see 2. above) should not hold a
> release if noone offers to fix it in *reasonable* time (e.g., range
> of days). Currently a couple of important fixes are still officially
> unpublished such as (nearly randomly selected):

[...]

> 
> Currently we have 132 unreleased fixes in 6.0-CVS. IMHO a pity to not
> make them available officially to the user community.

As a non-developers I also strongly vote for smaller release-cycles. As
Markus pointed out there are some pending bugs, but the 132 of resolved
fixes should be published ASAP.
This indicates also activity to other occasualy grass-users imho.

just my 0.02¢

Stephan

-- 
GDF Hannover - Solutions for spatial data analysis and remote sensing
Hannover Office      -     Mengendamm 16d      -     D-30177 Hannover
Internet: www.gdf-hannover.de      -      Email: holl at gdf-hannover.de
Phone : ++49-(0)511.39088507       -        Fax: ++49-(0)511.39088508