ken after revision 100 will potentially have the
bug all
branches taken prior to revision 100 will not. The problem
here is
that as the number of bugs and branches increase the job of
answering the question "does bug x appear in branch y?"
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
p track of the revision where bugs
>>were introduced. As a use case, 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
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
e job of
answering the question "does bug x appear in branch y?" becomes ever
more difficult.
As a possible solution we are considering modifying commit messages
to indicate the bugs introduced in each revision. It should then be
possible to answer the above question with a simple svn log + grep.
I would be interested to hear any feedback the community has on this.
Jonathan Oulds
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
ncrease the job of answering the question "does bug x appear in branch y?"
> becomes ever more difficult.
>
> As a possible solution we are considering modifying commit messages to
> indicate the bugs introduced in each revision. It should then be possible
> to answer the above question with a simple svn log + grep.
>
> I would be interested to hear any feedback the community has on this.
> Jonathan Oulds
>
>
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.
e the job of answering the question "does bug x
appear in branch y?" becomes ever more difficult.
As a possible solution we are considering modifying commit messages to
indicate the bugs introduced in each revision. It should then be
possible to answer the above question with a simple
10 matches
Mail list logo
