Re: Anyone recognise this fixed bug (subtext: where is the bug DB?)

Richard Foley wrote:

> > > email addresses (the cc list?) of the people who are also
> The cc list is being maintained for all bugs.
> When the status of a bug changes, do all on the cc list want to be notified
> (plus admins), (not p5p), or only when the bug is closed?

When it changes I guess.

> > I also think a bugfix should have to be logged and given some sort of
> > patch id before a bug will be marked as closed.  That way the pumpking
> > stands some vague chance of figuring out what was fixed by whom and
> > when.  I've always thought that the current mechanism of just firing a
> > patch at p5p and hoping it sticks is a bit hit and miss.  I am in awe of
> > the pumpkings who manage to wrest some order from the apparent chaos.
> We need to discuss this patchID a bit:
> Should it be a relation between ticketid and fixed_in_version
> (5.6.0.2_p01_20000321.001)
> Or should it be an unique (non-incrementing) ID?  (p_235354532)
> Or version_unique_patchid (5.6.0.3_45151)
> Or is there currently a standard patchID we can use that I don't know about?

I think it should just be an incrementing id.  You can't really put a
perl version it it anywhere because you don't know in advance if/when
the patchid was integrated, and a perl version number is therfore
misleading.  You can find the version the patch was raised against by
looking at the associated bug, which will have the perl version in it.

> > 7.  When the pumpking has finished producing a new release, he sends a
> > mail back to the bug DB with a list of the integrated patch IDs.  This
> > updates the status of all the revevant bugs in the database from 'fixed'
> > to 'integrated' and marks the bug with the release that the fix was
> > integrated into.
> Something along the lines of?:
> 
>         To: patch_<version>_<ticketid>_<ticketid>_<ticketid>[email protected]
> 
> or
> 
>         To: patch_<version>[email protected]
>         Subject: <ticketid> <ticketid> <ticketid> ...
> 
> or both or something else?

Why not just a list of patchids in the message body?

Alan Burlison