Thread: [Codestriker-user] Obsolete state
Brought to you by:
sits
Menu
▾
▴
codestriker-user
|
From: Craig J. <cra...@pr...> - 2004-10-12 05:29:48
|
David and others, I submitted a feature request some months ago regarding a new state such as "obsolete" be added to codestriker. This could then be used when a follow-up review is posted to indicate that it makes a previous one obsolete. The view of a review would also contain a link to all reviews made obsolete by this one and all reviews that make this one obsolete. Has this idea been considered? Is it of interest to anyone else? Cheers, Craig. |
|
From: David S. <si...@us...> - 2004-10-12 08:46:24
|
Hi Craig, > I submitted a feature request some months ago regarding a new state such > as "obsolete" be added to codestriker. This could then be used when a > follow-up review is posted to indicate that it makes a previous one > obsolete. The view of a review would also contain a link to all reviews > made obsolete by this one and all reviews that make this one obsolete. > > Has this idea been considered? Is it of interest to anyone else? For everyone's reference, this is the issue you raised: http://sourceforge.net/tracker/index.php?func=detail&aid=1008524&group_id=41136&atid=429863 I can definately see merit in the idea, I've just been busy with stacks of other stuff, I haven't had any time to look into it. Haven't said that, with the 1.8.4 release, you can do some of the things you want. If a topic becomes "obsolete", I would move it into state "closed". This makes the topic effectively read-only, so it will be obvious to people that they can't add comments to it. You can also modify the topic description / title to indicate it has become obsolete, and the URL of the topic that superseeds it. Likewise, the new topic can include URLs to the topic it has super-seeded. I know its not 100% what you asked for, but it is getting there. Cheers, David |
|
From: David S. <si...@us...> - 2004-10-12 23:20:28
|
> I submitted a feature request some months ago regarding a new state such > as "obsolete" be added to codestriker. This could then be used when a > follow-up review is posted to indicate that it makes a previous one > obsolete. The view of a review would also contain a link to all reviews > made obsolete by this one and all reviews that make this one obsolete. > > Has this idea been considered? Is it of interest to anyone else? Hi Craig, With the latest release of Codestriker, you can get pretty close to what you want I believe. When a topic is moved into state "closed" (or "committed") the topic effectively becomes read-only. In your situation, if you want to "obsolete" a topic, I would do the following: * Go to the topic properties page, and do the following: - Change to state "closed". - Prepend "OBSOLETE: " to the existing topic title. - Append the URL of the new Codestriker topic which replaces it into the topic description. When creating a new topic, you can also add the URL of the topic it obsoletes into the description. That way, you have your links, and it will be very clear to the reviewers when a topic has become obsolete. -- Cheers, David |
|
From: Craig J. <cra...@pr...> - 2004-10-12 23:49:22
|
Hi David, Thanks for the ideas. We do something similar to this at the moment, however we would like to see it automated as it is difficult to get a team of 40 developers to consistently follow a manual process. The more transparent we can make the process the better because when people get a bit slack and skip the steps you outline it kind of snowballs across the whole team and we are left with no obsolete feature. It is actually a rare site to see someone change the state to committed! It would be good to see a drop-down list containing the available topics in the "Create new topic" page or a new column in the topic list pages containing a "Create replacement topic" or something similar. Is this functionality easy to add to codestriker or would it take a fair amount of work? Cheers, Craig. On Wed, 2004-10-13 at 09:16, David Sitsky wrote: > > I submitted a feature request some months ago regarding a new state such > > as "obsolete" be added to codestriker. This could then be used when a > > follow-up review is posted to indicate that it makes a previous one > > obsolete. The view of a review would also contain a link to all reviews > > made obsolete by this one and all reviews that make this one obsolete. > > > > Has this idea been considered? Is it of interest to anyone else? > > Hi Craig, > > With the latest release of Codestriker, you can get pretty close to what > you want I believe. When a topic is moved into state "closed" (or > "committed") the topic effectively becomes read-only. > > In your situation, if you want to "obsolete" a topic, I would do the > following: > > * Go to the topic properties page, and do the following: > - Change to state "closed". > - Prepend "OBSOLETE: " to the existing topic title. > - Append the URL of the new Codestriker topic which replaces it into the > topic description. > > When creating a new topic, you can also add the URL of the topic it > obsoletes into the description. That way, you have your links, and it > will be very clear to the reviewers when a topic has become obsolete. -- Craig Jeffree Direct: +61 3 9426 8238 Software Engineer Reception: +61 3 9428 8899 Technical Services Fax: +61 3 9427 1969 Preston Aviation Solutions http://www.preston.net/ 488 Victoria St Richmond VIC, 3121 Helping our customers increase the efficiency, capacity and safety of the global aviation industry through the provision of integrated simulation, decision support and scheduling solutions. A BOEING COMPANY |
|
From: David S. <si...@us...> - 2004-10-13 01:13:38
|
> It would be good to see a drop-down list containing the available > topics in the "Create new topic" page or a new column in the topic list > pages containing a "Create replacement topic" or something similar. I think the latter approach is better. In fact, if we added a button to the bottom of the list screen with "Create replacement topic", then we can have a many-to-one association with obsoleting topics. I am not sure if this is realistic, but perhaps someone might want to obsolete several topics with a single new topic? Do you ever see that as being a possibility, or is that overkill? The create topic action would need to be modified, so that when created, it changes the obsoleted topics to state "closed". We'd have to have a new db table which records the obsoleted associations, and modify the view screens appropriately so that when displaying an obsoleted topic, we display a link to the new topic. If we can only obsolete a single topic at a time, we'd only need to add a new field in the topic table, rather than creating a new table, which would make life a bit easier. > Is this functionality easy to add to codestriker or would it take a > fair amount of work? Well, its certaintly not trivial, but it doesn't sound too bad either. -- Cheers, David |
|
From: Craig J. <cra...@pr...> - 2004-10-13 01:26:24
|
On Wed, 2004-10-13 at 11:09, David Sitsky wrote: > > It would be good to see a drop-down list containing the available > > topics in the "Create new topic" page or a new column in the topic list > > pages containing a "Create replacement topic" or something similar. > > I think the latter approach is better. In fact, if we added a button to > the bottom of the list screen with "Create replacement topic", then we can > have a many-to-one association with obsoleting topics. I am not sure if > this is realistic, but perhaps someone might want to obsolete several > topics with a single new topic? Do you ever see that as being a > possibility, or is that overkill? I think it would be a reasonable feature, certainly not overkill, but not a rare occurance either. > > The create topic action would need to be modified, so that when created, it > changes the obsoleted topics to state "closed". We'd have to have a new Would it not be wise to create a state of "obsolete" rather than using "closed"? > db table which records the obsoleted associations, and modify the view > screens appropriately so that when displaying an obsoleted topic, we > display a link to the new topic. And a link from the new topic back to the obsolete ones. Cheers, Craig. |
|
From: David S. <si...@us...> - 2004-10-13 03:52:22
|
> > The create topic action would need to be modified, so that when > > created, it changes the obsoleted topics to state "closed". We'd have > > to have a new > > Would it not be wise to create a state of "obsolete" rather than using > "closed"? Yep, they are distinct states. > > db table which records the obsoleted associations, and modify the view > > screens appropriately so that when displaying an obsoleted topic, we > > display a link to the new topic. > > And a link from the new topic back to the obsolete ones. Sure. -- Cheers, David |
Thanks for helping keep SourceForge clean.
X