About the author

Steven Harmansteven harman :: makes sweet software with computers!

For recent posts and more about me, scroll to the bottom.

Subscribe

  • Subscribe to my feed. via RSS
  • Subscribe via email via email

News

Badges

  • Subtext Project
  • Support Subtext

Calling All SourceForge Users

As many of you likely know, I am one of several [very talented] developers working on the subTEXT Project. As such I try to keep on top of our various Trackers and the items in them. If you take a look at our Bug Tracker you will notice that you can search and/or filter the items using a variety of predefined fields. One of these fields is labeled "Group".

What is "Group"?

SourceForge - Tracker - Group Field

The Group field is available in the Feature Request, Patch and (as I mentioned) the Bug Trackers. For the subTEXT project, the values for this field tend to be version numbers representing the the different release versions of subTEXT. Given that the fields hold version numbers it is pretty obvious what the first two Trackers use that group for:

  • Feature Requests: The release in which the Feature Request is scheduled to be/was delivered.
  • Patch: The release in which the Patch is scheduled to be/was delivered.

So here is my question: What is this field supposed to be used for... or even better, how does your (or other) project use this field in the Bug Tracker? If we continue with the idea of putting version numbers in there, then I see two possible uses for the field:

  • A: The release in which the Bug was discovered/opened.
  • B: The release in which the Bug fix was delivered, and therefor closed..

I tend to like option B as that would provide for better tracking down the road. What I mean is, you could at any time see what bugs were closed in what release, and also help to determine when a bug was supposedly closed. Although I do see where option A could be beneficial as well. But this isn't supposed to be about what I think... I want to know what YOU think.

So please leave some feedback with your thoughts, opinions, suggestions, yadda-yadda.

What others are saying.

# re: Calling All SourceForge Users
Gravatar Haacked
Jul 28, 2006
Personally, I think the person creating the bug report should use the version they found the bug.

The person closing the bug should change it to the version it was fixed in.

Then we know that the meaning of that field for open bugs is the version it was found in (helpful for us to test and reproduce). The meaning of that field for closed bugs is the version it was fixed in (helpful for generating release notes).

Speaking of which, we need to add 1.9 and "trunk" as options.
# re: Calling All SourceForge Users
Gravatar Steve Harman
Jul 28, 2006
Damn it Phil... why you gotta be so smart and show me up like that?

I would now like to retract my previous statement:
I tend to like option B...
And instead throw my support behind Phil's suggestion.
Comments have been closed on this topic.