Hi Abraham, On Mon, 2008-06-02 at 11:15 +0200, [EMAIL PROTECTED] wrote: > Is it necessary to see this information "in the bugtracker" ? Well, it is > in my case because of the way we work; I don't know whether other offices
I am not convinced. Why must such information, which are a dynamic property (can be renamed, deleted), be present IN the bugtracker as comments ? > test version. Now consultants need to know which issues' fixes are already > available for testing, and I thought adding notes to issues related with > tagged files would be an easy, quick, automatic and difficult-to-mistake > way. Consultants can know this information *without* that information being in the bug-tracker. The VDD Generator produces a document, in both pdf and html formats, that lists which fixes went into a release. This document provides the information you need. When you release on your test server, you could produce a VDD document and make it available on that server for the consultants to view. > Now the second part, behavior. I don't think it's necessary to find out > which files have changed nor which the previous tag was. In the very I disagree. > have the <file, version, bug> data, I can search the matching <file, > version> pairs and get related bug numbers; this would take into account > branches and file modifications. On the other hand, it's also true that How far back do you search ? At which version should you stop ? You don't know that unless you know *from* which version you are tagging. > P.S.: Should I update bug 1174 myself with this info? Do I have proper > perms? No, I'll update the bug. You don't have permissions.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
