Talk:Handling trackers - Revision history

Rben13: /* Proposal by Eric on policy */

2007-10-27T09:45:14Z

Proposal by Eric on policy

← Older revision		Revision as of 09:45, 27 October 2007
Line 89:		Line 89:

	-- [[User:Ewl\|Eric L.]] 12:19, 26 Oct 2007 (PDT)		-- [[User:Ewl\|Eric L.]] 12:19, 26 Oct 2007 (PDT)

			== Ray's Comments ==

			I think that the groups are a good way to do this. It's certainly worth trying out and seeing how well it works for us. We can always try something different if this doesn't work.

			I prefer the groups over the title tagging for all the reasons others have given, but especially because of the problems with spelling errors and consistency.

			If it turns out that we find this is insufficient, it is possible to look at other tracking systems, such as bugzilla, but I think our time is better spent getting the release done. Really big process changes, like using a new bug trackign system, are best started at the beginning of a new release cycle.

			Ray

Danielpolansky: /* Tagging of issues (counter-proposal based on groups) */

2007-10-26T20:05:24Z

Tagging of issues (counter-proposal based on groups)

← Older revision		Revision as of 20:05, 26 October 2007
Line 77:		Line 77:

	OK with me, only "con" I see is that we would have 2 groups per release. [[User:Ewl\|Ewl]] 11:44, 25 Oct 2007 (PDT)		OK with me, only "con" I see is that we would have 2 groups per release. [[User:Ewl\|Ewl]] 11:44, 25 Oct 2007 (PDT)

			==Proposal by Eric on policy==

			For each release being developed, we create two groups: one "FreeMind X.Y.Z" and one "FreeMind X.Y.Z - Fixed in CVS". We then use the groups in the following manner:

			; Note : for sake of simplicity, we assume X.Y.Z is the version being currently developed, and A.B.C an older version of FreeMind.

			# items with no or with older group like "FreeMind A.B.C" can be checked by helpers with sufficient rights, and closed if issue doesn't appear anymore in the latest beta/RC of X.Y.Z, else group is changed to the current version "FreeMind X.Y.Z".
			# items with current version group "FreeMind X.Y.Z" can be fixed by a developer, then moved into group "FreeMind X.Y.Z - Fixed in CVS".
			# testers check items with group "FreeMind X.Y.Z - Fixed in CVS", and close if OK (after next release), else setup back to group "FreeMind X.Y.Z".

			-- [[User:Ewl\|Eric L.]] 12:19, 26 Oct 2007 (PDT)

Danielpolansky: /* Tagging of issues (counter-proposal based on groups) */

2007-10-25T23:59:42Z

Tagging of issues (counter-proposal based on groups)

← Older revision		Revision as of 23:59, 25 October 2007
Line 57:		Line 57:
	'''Pros and cons:'''		'''Pros and cons:'''

	* Con: Users entering the bug tracking system see per default the items in the group "FreeMind 0.9.0", filtering away the issues solved in CVS. That may easily lead to the creation of duplicate bug reports. --[[User:Danielpolansky\|Dan Polansky]] 11:15, 25 Oct 2007 (PDT)		* <s>Con: Users entering the bug tracking system see per default the items in the group "FreeMind 0.9.0", filtering away the issues solved in CVS. That may easily lead to the creation of duplicate bug reports. --[[User:Danielpolansky\|Dan Polansky]] 11:15, 25 Oct 2007 (PDT)</s> That is false. --[[User:Danielpolansky\|Dan Polansky]] 16:59, 25 Oct 2007 (PDT)

	[[User:Ewl\|Ewl]] 04:43, 25 Oct 2007 (PDT)		[[User:Ewl\|Ewl]] 04:43, 25 Oct 2007 (PDT)

Ewl: /* Response: at least consistent naming */

2007-10-25T18:44:24Z

Response: at least consistent naming

← Older revision		Revision as of 18:44, 25 October 2007
Line 75:		Line 75:

	--[[User:Danielpolansky\|Dan Polansky]] 10:53, 25 Oct 2007 (PDT)		--[[User:Danielpolansky\|Dan Polansky]] 10:53, 25 Oct 2007 (PDT)

			OK with me, only "con" I see is that we would have 2 groups per release. [[User:Ewl\|Ewl]] 11:44, 25 Oct 2007 (PDT)

Danielpolansky: /* Tagging of issues (counter-proposal based on groups) */

2007-10-25T18:15:34Z

Tagging of issues (counter-proposal based on groups)

← Older revision		Revision as of 18:15, 25 October 2007
Line 57:		Line 57:
	'''Pros and cons:'''		'''Pros and cons:'''

	* Con: Users entering the bug tracking system see per default the items in the group "FreeMind 0.9.0", filtering ~~aways~~ the issues solved in CVS. That may easily lead to the creation of duplicate bug reports. --[[User:Danielpolansky\|Dan Polansky]] 11:15, 25 Oct 2007 (PDT)		* Con: Users entering the bug tracking system see per default the items in the group "FreeMind 0.9.0", filtering away the issues solved in CVS. That may easily lead to the creation of duplicate bug reports. --[[User:Danielpolansky\|Dan Polansky]] 11:15, 25 Oct 2007 (PDT)

	[[User:Ewl\|Ewl]] 04:43, 25 Oct 2007 (PDT)		[[User:Ewl\|Ewl]] 04:43, 25 Oct 2007 (PDT)

Danielpolansky: /* Tagging of issues (counter-proposal based on groups) */

2007-10-25T18:15:03Z

Tagging of issues (counter-proposal based on groups)

← Older revision		Revision as of 18:15, 25 October 2007
Line 55:		Line 55:
	next release), else setup back to group "FreeMind 0.9.0".		next release), else setup back to group "FreeMind 0.9.0".

	Pros and cons:		'''Pros and cons:'''

	* Con: Users entering the bug tracking system see per default the items in the group "FreeMind 0.9.0", filtering aways the issues solved in CVS. That may easily lead to the creation of duplicate bug reports.		* Con: Users entering the bug tracking system see per default the items in the group "FreeMind 0.9.0", filtering aways the issues solved in CVS. That may easily lead to the creation of duplicate bug reports. --[[User:Danielpolansky\|Dan Polansky]] 11:15, 25 Oct 2007 (PDT)

	[[User:Ewl\|Ewl]] 04:43, 25 Oct 2007 (PDT)		[[User:Ewl\|Ewl]] 04:43, 25 Oct 2007 (PDT)

Danielpolansky: /* Tagging of issues (counter-proposal based on groups) */

2007-10-25T18:14:38Z

Tagging of issues (counter-proposal based on groups)

← Older revision		Revision as of 18:14, 25 October 2007
Line 55:		Line 55:
	next release), else setup back to group "FreeMind 0.9.0".		next release), else setup back to group "FreeMind 0.9.0".

	~~; TBD : list pros~~ and cons...		Pros and cons:

			* Con: Users entering the bug tracking system see per default the items in the group "FreeMind 0.9.0", filtering aways the issues solved in CVS. That may easily lead to the creation of duplicate bug reports.

	[[User:Ewl\|Ewl]] 04:43, 25 Oct 2007 (PDT)		[[User:Ewl\|Ewl]] 04:43, 25 Oct 2007 (PDT)

Danielpolansky: /* Tagging of issues */

2007-10-25T18:02:31Z

Tagging of issues

← Older revision		Revision as of 18:02, 25 October 2007
Line 26:		Line 26:

	*Pro: Tagging is flexible, unlike the use of categories and other attributes.		*Pro: Tagging is flexible, unlike the use of categories and other attributes.
			*Pro: SF bug tracker provides only two generic attributes: group and category. Tagging makes more logical attributes possible.
	*Con: There is no way to restrict the tags used. (Eric, edited by Dan)		*Con: There is no way to restrict the tags used. (Eric, edited by Dan)
	*Con: Tagging is vulnerable to typos, like "SVCS" instead of "SCVS", and 'false friends', like "FreeMind'sCVS" containing "SCVS". (Eric, edited by Dan)		*Con: Tagging is vulnerable to typos, like "SVCS" instead of "SCVS", and 'false friends', like "FreeMind'sCVS" containing "SCVS". (Eric, edited by Dan)

Danielpolansky: /* Tagging of issues */

2007-10-25T17:58:23Z

Tagging of issues

← Older revision		Revision as of 17:58, 25 October 2007
Line 26:		Line 26:

	*Pro: Tagging is flexible, unlike the use of categories and other attributes.		*Pro: Tagging is flexible, unlike the use of categories and other attributes.
	*Con: There is no way to restrict the tags used. --Eric		*Con: There is no way to restrict the tags used. (Eric, edited by Dan)
	*Con: Tagging is vulnerable to typos, like "SVCS" instead of "SCVS", and 'false friends', like "FreeMind'sCVS" containing "SCVS". --Eric		*Con: Tagging is vulnerable to typos, like "SVCS" instead of "SCVS", and 'false friends', like "FreeMind'sCVS" containing "SCVS". (Eric, edited by Dan)
	*Con: Tagging uses up the title length, necessitating the shortening of the title in some cases.		*Con: Tagging uses up the title length, necessitating the shortening of the title in some cases.

Danielpolansky: /* Tagging of issues */

2007-10-25T17:58:01Z

Tagging of issues

← Older revision		Revision as of 17:58, 25 October 2007
Line 26:		Line 26:

	*Pro: Tagging is flexible, unlike the use of categories and other attributes.		*Pro: Tagging is flexible, unlike the use of categories and other attributes.
	*Con: There is no way to restrict the tags used.		*Con: There is no way to restrict the tags used. --Eric
	*Con: Tagging is vulnerable to typos, like "SVCS" instead of "SCVS", and 'false friends', like "FreeMind'sCVS" containing "SCVS".		*Con: Tagging is vulnerable to typos, like "SVCS" instead of "SCVS", and 'false friends', like "FreeMind'sCVS" containing "SCVS". --Eric
	*Con: Tagging uses up the title length, necessitating the shortening of the title in some cases.		*Con: Tagging uses up the title length, necessitating the shortening of the title in some cases.