On Wed, 2006-11-15 at 08:35 +0000, Robert G Ward wrote:
> Thanks for the suggestion.
> 
> This is kind of what I am doing at the moment, but an autogenerated PDF
> report I can stick under my bosses nose would demonstrate that nothing is
> getting missed.

I'm with you there.

> As a fallback, I am writing my own custom script that is writing every
> commit message into a mysql database (actually the bugzilla one!) so I can
> query the information myself.   

Perhaps I spoke too soon. If your tag names didn't match a numbering
convention, you wouldn't be able to determine the differences between
two tags. You might miss commits on a tag that was applied between tag 1
and tag2 if that intermediate tag had a name that didn't match some
naming convention. You'd have to:

cvs log -r tag1 -r tag2

and then parse the output to collect the bug numbers. And report only
the changes shown by this cvs log. You may be able to use the commit
dates reported by cvs log to then cross reference the bug-tracker, if
you wanted to be more precise in reporting the status of the bug at the
time, severity, other metadata.

But this seems to be the approximation cvs2cl does, and most likely the
one Scmbug would have to reimplement. We could pick the earliest and
letest commit dates. And then again, the result could still be slightly
wrong if the SCM repository and the bugtracker machines have a
mismatching time by a few seconds.

> I've not really got this working - has anyone else tried something similar

I wish you took scmbug_vdd_generator as the basis of starting all this
work. We'd love to have some, any really, solution to this merged-in.

The CVS mailing list is [email protected]

CVS should really implement storing the date a tag was applied. I'm
sending them another email requesting this, right now.

Another reliable solution would be to... completely ignore CVS's lack of
this feature and implement it within Scmbug. When a tag is applied, save
in CVSROOT/var/scmbug/tag_dates.txt the date the tag was applied. This
would make this feature applicable to older CVS installations (1.11.x)
assuming tags were applied when Scmbug was installed.

It wouldn't help with your current problem though.

_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to