[Ffmpeg-devel] Re: Advocating periodic releases

[Michael Niedermayer]

Hi

On Fri, Oct 13, 2006 at 02:27:04PM -0400, Dana Hudes wrote:
> Michael Niedermayer wrote:
> >Hi
> >
> >On Thu, Oct 12, 2006 at 07:51:05PM -0700, Roman Shaposhnick wrote:
> >  
> >>Hi
> >>
> >>On Wed, 2006-10-11 at 11:47 +0200, Michael Niedermayer wrote:
> >>    
> >>>state diagram copy & pasted from an old bugzilla flame ...
> >>>----------
> >>>Bugs:
> >>>   /<--------------------------\
> >>>New -> Verified -> Analyzed -> Fixed (-> Fixed&Checked)
> >>>^\\\-> WorksForMe  | |     \-> WontFix
> >>>| \--> Duplicate <-/ |
> >>>v  --> Invalid <-----/
> >>>NeedMoreInfo
> >>>      
> >>  This seems quite reasonable. 
> >>
> >>    
> >>>Patches:
> >>>   /<-(reverse)-\
> >>>New -> Ok -> Applied (->Applied&Checked)
> >>>^  \-> Rejected
> >>>|
> >>>v
> >>>NeedsChanges
> >>>      
> >>  I'm sorry, but how do patches tie in into bugtracking ? 
> >>    
> >
> >patchtracking :)
> >of course the idea is optional, and unrelated but it was part of the
> >original bugzilla flame from where i copy and pasted the stuff above
> >
> >
> >  
> A fix would indicate which SVN revision of which file(s) is needed to 
> fix the bug. I would expect this information in the resolution. 

mentioning the svn revision which fixed the bug seem like a good idea
and theres no need to mention files as svn revisions are global


> I would 
> also expect the ticket not be closed until independently verified -- 
> either by original requestor or the monitor(s).

theres no closed state in my proposal, and i also see no sense in one

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is