GRASS bugs (was: [GRASS-dev] GRASS 6.1.0 branch status)

[Paolo Cavallini]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all.
I have a slightly different view here: although it is agreed that the
bug report is not an advertising tool, it is clear that new and
institutional potential users, as well as potential bugfixers, are
scared by very long queues of bugs, especially if:
- - most of them do not have an owner (so one can expect they'll not be
fixed soon)
- - many are very old (> 1 yr, up to > 4yr!).
I think the current approach mixes two different needs:
- - a bug tracking system
- - a knowledge base.
I think it is better to separate more clearly the two.
I would therefore suggest to close (as unreproducible/wontfix etc.)
*all* old bugs; we should not worry about losing relevant info, because
they stay on the database - they just don't show on the usual reports,
but can be easily checked and reopened if necessary.
The best bug reporting tool I'm using is Trac, used eg by qgis:
http://svn.qgis.org/trac/report/
very easy to use, powerful, and reports can be customized easily. Could
we move to this? Qgissers have done he transition not long ago, so they
could give us hints if necessary. A trac package is present eg in
Debian, so installation should pose no major problems.
I think this should be done before the bugsquishing party, in order to
have a more flexible tool and make the work more effective.
I'm ready to cooperate on this.
pc

Maciej Sieczka ha scritto:
> 
> As soon as the schedule is settled I'd like to spread the news on
> mailing lists to ask all Grass bug reporters to take a look into their
> old BT tickets and update the information there if possible. I think we
> should give folks at least about 5 working days for this before the bug
> fiesta begins (it's summer time so we might not reach many people but
> anyway we should try to have as good background as possible).
> 
>> Some older bugs IMHO could be closed as WONTFIX i.e. GUI related bugs for 5.x 
>> series.
> 
> Just ignore anything that is not assigned to area 'grass6'. There was a
> reasonable effort to assign 'grass6' to all bugs still relevant. Use the
> interface in the bottom of
> https://intevation.de/rt/webrt?logout=guest&q_queue=grass to filter the
> list.
> 
> I wouldn't go closing old bug, grass5.4, wish etc. entries just to get
> rid of them not fixing them. Let's keep them open for knowledge about
> the old versions, they do no harm.
> 
> Many grass6 bugs miss feedback from reporters and enough information to
> be able to reproduce them. OTW their status is uncertain, though I don't
> think it makes sense to close them only for that. So maybe I'll go and
> assign Current priority '0' to such tickets first, so we can easily
> ignore them but still have them open just in case?
- --
Paolo Cavallini
email+jabber: cavallini at faunalia.it
www.faunalia.it
Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy   Tel: (+39)348-3801953
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE0E1y/NedwLUzIr4RAvf3AJ4nvIDukMZ6KieWd9SeI9wllREV2ACgj8B6
cl/utIof5mdXGCJSdR1ow7g=
=Rq2t
-----END PGP SIGNATURE-----