> -----Original Message----- > From: Scott Eade [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 20, 2003 10:50 PM > To: turbine-dev > Subject: Re: Proposed Scarab chnages > > > On 21/03/2003 2:38 AM, "Quinton McCombs" > <[EMAIL PROTECTED]> wrote: > > > Anyone else have any comments on this? > > > >> -----Original Message----- > >> > >> Issue types: > >> > >> Remove the Feature, Task, and Patch issue types. All > issues can be > >> classified as a Defect or an Enhancement. Patches should > always be > >> attached to a Defect or an Enhancement issue. > I quite liked the idea of Patch - a diligent committer that > wanted to keep an eye on and apply patches could just check > for open Patch issues. OTOH it is not like the volume of > issues is at all significant and the way Scarab separates the > issue types is quite annoying.
Perhaps we could add an additional attribute to the issues that would indicate if a patch is supplied. This would allow us to have a saved query that would report all open issues with a column to inidcate if a patch was included. > The Task issue type could be useful as a container issue for > doing something like a release (make all issues that are > intended to be resolved for a release children of a task > issue). Once again, the volume of issues is low so this is > probably overkill. I like this idea... However Scarab does not provide any way that I know of to report on something like this. You could accomplish the same goal with an attribute holding the target milestone. For example, all of the issues that need to be resolved for a release could have the version number in this attribute. You could then create a query showing all open issues for that release. This is the Scarab self hosting version appears to be setup. > A Feature is just a large Enhancement - no reason for it not to go. Very true. However, what is the difference? How would someone know if they should create an enhancement or a feature issue? If Scarab had better support for reporting on dependant issues, the a feature could serve as a container for multiple enhancements. This would be a good thing... If Scarab had support for this. > <snip/> > > All of the remaining suggestions look good, assuming Scarab > can accommodate them. It can. I have been using Scarab for issue tracking in-house for since beta-8. Nearly everything that I am proposing is what I have been using with the exception of the voter user attribute. The only place where it gets a little messy is the drop downs for version numbers. This will be a global attribute that contains the version numbers used by ALL modules in the scarab instance. At the module level, we will include the ones applicable for the the modules. > I have Scarab admin access, but I am wary of making changes > without some involvement by John McNally. If you recall I > sought John's input when the addition of the version field > was discussed some time ago, but no response was received. > Not sure where John is at lately - I haven't seen any posts > from him anywhere for some time now. > I would certainly like for him to give his blessing to the idea considering his knowledge of Scarab. It might also make sense to see if he can help us upgrade to the latest version. If you have noticed selecting an issue from a query is incedibly slow. This is due to very inefficient code in the section that displays the previous and next links for the issue. This has been fixed in CVS head which appears to be very stable. I think that a combination of the changes that I have proposed and upgrading the version will help get more people using the issue tracking system. It can add a great deal of value for this project. > Scott > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au .Mac Chat/AIM: > seade at mac dot com > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
