Moisei Rabinovich 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?]
Yes, we need to somehow obsolete the original topic with the new topic.
This is easy to do if the topics are created "by hand", but via the
SCM commit hook, we need to handle this in a different way.
I can see a couple of options here, which Jason has already eluded to:
* In the topic description, we could perhaps introduce another magical
auto-link text, so that if you type in Topic 73514332, this would
automatically hyperlink to that topic. We actually do this with Bug
XXXX text if a bug tracker has been enabled.
That way, the developer can add the Topic XXXXXXX text to their commit
message, as a way of linking topics together.
They can actually do this today, just by adding a full hyperlink to the
topic they are obsoleting, as Codestriker will render hyperlinks
* Another option would be to have a new field in the topic properties
tab, something like "Superseeds Topics: XXXXXX", as a way of creating an
obsolete link directly. The onus would be on somebody to then update
this field to maintain your links.
Does anyone else have any other ideas?