Difference between revisions of "Bug tracking"

From GRASS-Wiki
Jump to: navigation, search
(Introduction: corrections)
(cleaning (gforge is dead))
Line 11: Line 11:
 
The GForge and RT GRASS trackers can be used to examine the previously resolved issues, and those that were still in progress as the new system was released. It would be good to move all the tickets from the former trackers to the new one, but nobody has volunteered yet. If you are the one, please contact the admin to arrange it.
 
The GForge and RT GRASS trackers can be used to examine the previously resolved issues, and those that were still in progress as the new system was released. It would be good to move all the tickets from the former trackers to the new one, but nobody has volunteered yet. If you are the one, please contact the admin to arrange it.
  
=== Participate ===
+
== See also ==
  
The trackers are available for public view, but in order to be able to post (including creating a new report), and to use all the features of the trackers, you need to [http://wald.intevation.org/account/register.php setup an account at GForge] and [http://wald.intevation.org/project/request.php?group_id=21 join the GRASS project at GForge].
+
* http://grass.osgeo.org/bugtracking/index.php
 
+
* http://trac.osgeo.org/grass/wiki
 
 
=== How it works ===
 
 
 
All trackers' new submissions are automatically forwarded to the [http://grass.itc.it/community/support.php#devellists GRASS development mailing list]. The followup traffic is stored in the tracker, and forwarded only to parties discussing the ticket. However, any project member can "monitor" a ticket, or a whole tracker, in order to receive all the related traffic (see [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]).
 
 
 
 
 
Maintainers:
 
;general admin and cleaner
 
:[[User:msieczka|Maciej Sieczka]]
 
;backup admin
 
:[http://wald.intevation.org/users/bernhard Bernhard Reiter]
 
;code patches
 
:Jachym Cepicky
 
;website patches
 
:Scott Mitchell
 
;doc patches
 
:[[User:Landa|Martin Landa]]
 
 
 
 
 
There are 3 project member roles: ''admin'', ''developer'' and ''user''.
 
 
 
; ''admin'': Manages requests to join the project and maintains the GRASS project's setup at GForge.
 
 
 
; ''developer'': Can do most of the things that admin can. Only that he doesn't have his duties and he can't remove the whole GRASS project. But he still can add/modify/delete trackers as well as delete tickets for good. It was neccessary to provide that much power to ''developers'' so that they could move tickets between the trackers. ''Developers'' - please use your power wisely and let the admin know before doing something more intrusive you are not sure about :).
 
 
 
; ''user'': Can open new tickets in the trackers, reply to other tickets and ''monitor'', participate in surveys (''admin'' and ''developer'' can too, of course).
 
 
 
 
 
=== Buggy bugtracker? ===
 
 
 
When you spot something wrong or a possible enhacement in the setup of GRASS trackers at GForge, please drop admin a line. If it's a bug or a missing feature in the GForge software itself, please report it to [http://wald.intevation.org/projects/siteadmin wald.intevation.org GForge site maintainers], preferably using [http://wald.intevation.org/tracker/?atid=162&group_id=1&func=browse their bugtracker]. If unsure whether the issue is in the GRASS trackers setup, or in the GForge itself, contact admin first, or ask on [http://grass.itc.it/devel/index.php#list GRASS dev ML].
 
 
 
Current top issues with GForge from the point of view of GRASS team, which hamper info flow and productivity:
 
 
 
* [http://wald.intevation.org/tracker/index.php?func=detail&aid=300&group_id=1&atid=162 can't CC an email from GForge]
 
* <strike>[http://wald.intevation.org/tracker/index.php?func=detail&aid=360&group_id=1&atid=162 whole discussion included in the email notification = noise]</strike> ''fixed by Sascha Wilde on 18.07.2007''
 
* [http://wald.intevation.org/tracker/index.php?func=detail&aid=85&group_id=1&atid=162 mail reply doesn't work]
 
* <strike>[http://wald.intevation.org/tracker/index.php?func=detail&aid=286&group_id=1&atid=162 email notifications sent from GForge to GRASS dev ML should also have it's address to reply to]</strike> ''fixed by Sascha Wilde on 30.07.2007''
 
 
 
=== GForge: beyond the trackers ===
 
 
 
GForge provides many functionalities. Currently we use only the trackers, as all the other functionalities are implemented in the current GRASS infrastructure (besides surveys; maybe there will be some use for them - let's keep them in mind  :)  ). However, it is worth rembering that GForge can provide things like discussion forums, mailing lists, ftp space, SVN server and some more.
 
 
 
''NOTE, 2007.04.07: according to [http://www.nabble.com/d.menu%2C-d.ask-tf3385241.html#a9832649 discussion on GRASS dev ML], [[SVN hosting|migration to SVN]] is planned soon.''
 
 
 
 
 
 
 
=== More info ===
 
 
 
* [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]
 
* [http://grass.itc.it/bugtracking/index.php bugtracking page] on the GRASS website
 
* New ideas about GRASS 7 [[SVN hosting]]
 
  
 
[[Category: Development]]
 
[[Category: Development]]
 
[[Category: Community]]
 
[[Category: Community]]

Revision as of 16:37, 12 April 2008

Introduction

Currently we use Trac. Trac is an open source, web-based project management and bug-tracking tool, inspired by CVSTrac. It is developed and maintained by Edgewall Software.

http://trac.osgeo.org/grass

The former tracker was GForge (a feature-rich system for collaborating on a software project). Under the GForge setup by Intevation company, there is a set of trackers for the GRASS project.

There is also old GRASS Request Tracker.

The GForge and RT GRASS trackers can be used to examine the previously resolved issues, and those that were still in progress as the new system was released. It would be good to move all the tickets from the former trackers to the new one, but nobody has volunteered yet. If you are the one, please contact the admin to arrange it.

See also