Bug tracking - Revision history

Neteler: /* GitHub issues (2020 - present time) */ + Migrating GRASS code repository from SVN to git

2026-06-23T21:44:41Z

GitHub issues (2020 - present time): + Migrating GRASS code repository from SVN to git

← Older revision		Revision as of 21:44, 23 June 2026
Line 11:		Line 11:
	* announcement: https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/		* announcement: https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/
	* notes: https://neteler.org/blog/remarks-on-svn-trac-to-github-migration/		* notes: https://neteler.org/blog/remarks-on-svn-trac-to-github-migration/
			* Migrating GRASS code repository from SVN to git: https://trac.osgeo.org/grass/wiki/GitMigration

	=== trac (2007 - 2020) ===		=== trac (2007 - 2020) ===

Neteler: linked notes on SVN-trac to GitHub migration

2026-06-23T21:43:28Z

linked notes on SVN-trac to GitHub migration

← Older revision		Revision as of 21:43, 23 June 2026
Line 8:		Line 8:
	:'''https://github.com/OSGeo/grass/issues'''		:'''https://github.com/OSGeo/grass/issues'''

	See announcement: https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/		See
			* announcement: https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/
			* notes: https://neteler.org/blog/remarks-on-svn-trac-to-github-migration/

	=== trac (2007 - 2020) ===		=== trac (2007 - 2020) ===

Neteler: fix URL of https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/

2026-06-23T21:40:54Z

fix URL of https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/

← Older revision		Revision as of 21:40, 23 June 2026
Line 8:		Line 8:
	:'''https://github.com/OSGeo/grass/issues'''		:'''https://github.com/OSGeo/grass/issues'''

	See announcement: https://grass.osgeo.org/news/~~88/15/GRASS-GIS-issues-now-on-GitHub~~/		See announcement: https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/

	=== trac (2007 - 2020) ===		=== trac (2007 - 2020) ===

Neteler: fix order

2020-04-05T21:23:27Z

fix order

← Older revision		Revision as of 21:23, 5 April 2020
Line 24:		Line 24:
	The former tracker was [http://gforge.org GForge] (a feature-rich system for collaborating on a software project). Under the [http://wald.intevation.org/ GForge setup by Intevation company], there is a [http://wald.intevation.org/tracker/?group_id=21 set of trackers for the GRASS project].		The former tracker was [http://gforge.org GForge] (a feature-rich system for collaborating on a software project). Under the [http://wald.intevation.org/ GForge setup by Intevation company], there is a [http://wald.intevation.org/tracker/?group_id=21 set of trackers for the GRASS project].

	==~~= Request Tracker RT (2000 - 2006) ===~~		==== Participate ====

	~~Used: Dec 2000 - Dec 2006~~

	~~There is also the even older [https://web.archive.org/web/20070630161517/http://intevation.de/rt/webrt?q_status=open&q_queue=grass GRASS Request Tracker] - RT.~~

	~~=== Bug tracking in early days (1982 - 1999)~~ ===

	~~The entire bug tracking was done manually, through emails (with focus on the mailing lists).~~

	=~~= Participate~~ ==

	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].		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].

	=== GForge: How it works ===		==== GForge: How it works ====

	''(note: historic section)''		''(note: historic section)''
Line 65:		Line 55:
	; ''user'': Can open new tickets in the trackers, reply to other tickets and ''monitor'', participate in surveys (''admin'' and ''developer'' can too, of course).		; ''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 GForge bugtracker? ===		===== Buggy GForge 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].		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].
Line 76:		Line 66:
	* <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''		* <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: 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.		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.''		''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.''


			=== Request Tracker RT (2000 - 2006) ===

			Used: Dec 2000 - Dec 2006

			There is also the even older [https://web.archive.org/web/20070630161517/http://intevation.de/rt/webrt?q_status=open&q_queue=grass GRASS Request Tracker] - RT.

			=== Bug tracking in early days (1982 - 1999) ===

			The entire bug tracking was done manually, through emails (with focus on the mailing lists).

	== See also ==		== See also ==

Neteler: /* How it works */

2020-04-05T21:21:28Z

How it works

← Older revision		Revision as of 21:21, 5 April 2020
Line 38:		Line 38:
	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].		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].

	=== How it works ===		=== GForge: How it works ===

			''(note: historic section)''

	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]).		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]).
Line 62:		Line 64:

	; ''user'': Can open new tickets in the trackers, reply to other tickets and ''monitor'', participate in surveys (''admin'' and ''developer'' can too, of course).		; ''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 GForge bugtracker? ===		=== Buggy GForge bugtracker? ===

Neteler: /* Request Tracker RT (2000 - 2006) */ +Bug tracking in early days (1982 - 1999)

2020-04-05T21:19:49Z

Request Tracker RT (2000 - 2006): +Bug tracking in early days (1982 - 1999)

← Older revision		Revision as of 21:19, 5 April 2020
Line 29:		Line 29:

	There is also the even older [https://web.archive.org/web/20070630161517/http://intevation.de/rt/webrt?q_status=open&q_queue=grass GRASS Request Tracker] - RT.		There is also the even older [https://web.archive.org/web/20070630161517/http://intevation.de/rt/webrt?q_status=open&q_queue=grass GRASS Request Tracker] - RT.

			=== Bug tracking in early days (1982 - 1999) ===

			The entire bug tracking was done manually, through emails (with focus on the mailing lists).

	== Participate ==		== Participate ==

Neteler: Bug tracking now at GitHub

2020-04-05T21:17:52Z

Bug tracking now at GitHub

← Older revision		Revision as of 21:17, 5 April 2020
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

	=== trac (2007 - ~~present time~~) ===
			=== GitHub issues (2020 - present time) ===

			Jan 23, 2020, we switched from trac to GitHub also for the bug tracking (now called "issues").

			:'''https://github.com/OSGeo/grass/issues'''

			See announcement: https://grass.osgeo.org/news/88/15/GRASS-GIS-issues-now-on-GitHub/

			=== trac (2007 - 2020) ===

	Since 9 Dec 2007 we use '''Trac'''. [http://trac.edgewall.org Trac] is an open source, web-based project management and bug-tracking tool, inspired by CVSTrac. It is developed and maintained by Edgewall Software.		Since 9 Dec 2007 we use '''Trac'''. [http://trac.edgewall.org Trac] is an open source, web-based project management and bug-tracking tool, inspired by CVSTrac. It is developed and maintained by Edgewall Software.
Line 9:		Line 18:
	Historical note: The GForge and RT 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 nodody has volunteered yet. If you are the one, please contact the admin to arrange it.		Historical note: The GForge and RT 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 nodody has volunteered yet. If you are the one, please contact the admin to arrange it.

	=== GForge ===		=== GForge (2007 - 2008) ===

	Used: Jan 2007 - Dec 2008		Used: Jan 2007 - Dec 2008
Line 15:		Line 24:
	The former tracker was [http://gforge.org GForge] (a feature-rich system for collaborating on a software project). Under the [http://wald.intevation.org/ GForge setup by Intevation company], there is a [http://wald.intevation.org/tracker/?group_id=21 set of trackers for the GRASS project].		The former tracker was [http://gforge.org GForge] (a feature-rich system for collaborating on a software project). Under the [http://wald.intevation.org/ GForge setup by Intevation company], there is a [http://wald.intevation.org/tracker/?group_id=21 set of trackers for the GRASS project].

	=== RT ===		=== Request Tracker RT (2000 - 2006) ===

	Used: Dec 2000 - Dec 2006		Used: Dec 2000 - Dec 2006

Neteler: /* See also */ +URL OSGeo Project Infrastructure Migration 2007

2019-03-30T09:59:32Z

See also: +URL OSGeo Project Infrastructure Migration 2007

← Older revision		Revision as of 09:59, 30 March 2019
Line 72:		Line 72:
	* GRASS GIS [[Migration from CVS to SVN]]		* GRASS GIS [[Migration from CVS to SVN]]
	* GRASS GIS 7 [[SVN hosting]]		* GRASS GIS 7 [[SVN hosting]]
			* OSGeo: [https://wiki.osgeo.org/wiki/Project_Infrastructure_Migration_2007 Project Infrastructure Migration 2007]
	* [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]		* [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		* [http://grass.itc.it/bugtracking/index.php bugtracking page] on the GRASS website

Neteler: /* See also */+ Migration from CVS to SVN

2019-03-30T09:55:10Z

Neteler: Neteler moved page Tracking to Bug tracking: less confusing page title

2019-02-07T13:11:13Z

Neteler moved page Tracking to Bug tracking: less confusing page title

← Older revision	Revision as of 13:11, 7 February 2019
(No difference)

← Older revision		Revision as of 09:55, 30 March 2019
Line 70:		Line 70:
	== See also ==		== See also ==

	* GRASS 7 [[SVN hosting]]		* GRASS GIS [[Migration from CVS to SVN]]
			* GRASS GIS 7 [[SVN hosting]]
	* [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]		* [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		* [http://grass.itc.it/bugtracking/index.php bugtracking page] on the GRASS website