Branch Intelligence in Bugzilla

Max Kanat-Alexander mkanat at
Thu Jul 27 21:42:04 UTC 2006

On Thu, 2006-07-27 at 12:15 +0200, Robert Kaiser wrote:
> How do we make sure then that bugs that had been targeted (planned) to 
> be fixed in that release and actually didn't make it are not mistakenly 
> marked as fixed when the release is actually out?

	Because bugs get marked as FIXED when they're checked into CVS (or
whatever SCM you're using), not when a release comes out. So at the time
that somebody marks the bug as FIXED...oh, I see what you mean--do you
mean that some organizations fix the branches at a different time than
they fix the trunk?

	In that case you're probably right that it would be advantageous to
note that something has actually *been* fixed on a branch. Does that
actually happen that frequently, though, that something is fixed on the
trunk but not on a branch? Usually in that case I just leave a bug open,
and leave a comment on it...

	Anybody have a better idea that wouldn't involve making the proposed
"branch" fields more complicated?

Competent, Friendly Bugzilla Services. And Everything Else, too.

More information about the developers mailing list