Okay, I see what you are driving at here.
We write a script that takes the branch URL plus the buglist file, the
script performs an svn log -g -v to get a list of all the revision
numbers that went into that branch then compares those against the head
revision of the buglist file.
Yes, that
We do use Bugzilla to track issues, you are correct that you can file
the bug against multiple branches and we do.
However, what if a branch is created after the bug has been added to
Bugzilla. Someone would have to manually inspect the revision at which
the branch was taken and create anothe
Guten Tag Jonathan Oulds,
am Donnerstag, 13. Januar 2011 um 17:46 schrieben Sie:
> Currently we track bug fixes by including a reference number within the
> commit message, I'm sure this is common practice.
If you already use a bug tracker, doesn't that provide a mechanism to
file bugs against mu
Where is the bug file versioned? I think that is the point. In my opinion it
should not be versioned across branches because that would be a headache.
Hence it should not be placed under the trunk and you might create a new
directory "bugs" at the same level that trunk, tags and branches. In that
w
On 13/01/2011 20:08, Ryan Schmidt wrote:
On Jan 13, 2011, at 10:46, Jonathan Oulds wrote:
consider a project with many branches and tags, now imagine that a bug is
discovered to have been introduced at an early stage of the project e.g.
revision 100. All branches taken after revision 100
Thank you for your response,
The problem with keeping a versioned list of bugs in a file is that it
only allows you to update the list in the revision that relates to the
day you found the bug, and not the day you caused the bug.
Example:
The head of /trunk is at revision 500, I have three br
On Jan 13, 2011, at 10:46, Jonathan Oulds wrote:
> consider a project with many branches and tags, now imagine that a bug is
> discovered to have been introduced at an early stage of the project e.g.
> revision 100. All branches taken after revision 100 will potentially have
> the bug all bra
I think it will work but you don't need to change the commit message to
achieve that. You can create a plain text file (bug list) and versioning it
in Subversion.
For example, you may use this simple format:
...
bug x: r1, r2, r3
bug y: r2, r7
.
and look for revision numbers in the list
It's an intriguing prospect. I am assuming you're referring to the
revision where the bug was discovered. For example, I might have a
defect that's been in my system for years, but didn't know about it
until release 2.1.0 came out.
It's not hard to do, and may be useful. I've never done it myself.
