Re: [Codestriker-user] question on the general review workflow

[Jason R. <jre...@ya...>]

Hi,

The obsoleted feature is for this kind of thing. Really it depends on what you are using
codestriker for. It can be used to just keep an eye on things with an occasional comment added, to
a full blown inspection system with metrics and tracked resolutions for each comment. The fact
that you are creating topics with a hook suggests you are near the "keep an eye on things" side of
the spectrum, in which case it may not be worth the extra work to put the relationship between the
topics. We don't have a way of obsoleting topics automatically (though this could be added with
some changes to codestrker and check in comment discipline). Unless you are going to spend a lot
of time doing inspections and tracking comment resolutions it is probably not worth the worth to
obsoleting older topics.

However, it would help to have some more context on what you expect to get from codestriker. 

Thanks
Jason.

--- Moisei Rabinovich <mo...@gm...> wrote:

> Hello dear all,
> I've setup the subversion hook to create a new topic in codestriker on every
> commit and it works just fine.
> Now, I am looking for a god way to "link" the commits done based on the
> review to the original topic.
> Is there some recommended way?
> 
> The scenario is like:
> developer commit some code [new topic created]
> the reviewer mention the problem in file X1 line Y1 and file X2 line Y2
> [mails sent]
> the developer fixes the X1,Y1 and commits [new topic is created.... not so
> good... it still relates to the origibal topic... should the original one be
> obsoleted byt he new one?]
> 
> Please advise,
> -- 
> Best Regards,
> Moisei
> > > _______________________________________________
> Codestriker-user mailing list
> Cod...@li...
> https://lists.sourceforge.net/lists/listinfo/codestriker-user
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com