Re: [Audacity-devel] [Audacity-quality] Feature freeze (semifredo) from 24th Jan to 2nd Feb

[James C. <cr...@in...>]

I've taken this to the wiki:
http://wiki.audacityteam.org/wiki/Release_Policy

--James.

On 16/01/2010 01:29, Gale Andrews wrote:
> Am sending this back to -devel as seems currently correct.
>
> | From James Crook<cr...@in...>
> | Wed, 13 Jan 2010 11:58:32 +0000
> | Subject: [Audacity-quality] [Audacity-devel] Feature freeze (semifredo) from 24th Jan to 2nd Feb
>    
>> On 13/01/2010 05:24, Gale Andrews wrote:
>>
>>      
>>> IMO we should have released about the 3rd or 4th...
>>> As to how to avoid these sort of issues in future, I'm still saying the
>>> best way is to target release dates to the "bugs fixed and outstanding"
>>> position, not to circles on a calendar.
>>>        
>> If we have certain bugs agreed as being 'must fix' for next beta release
>> then that is as far as I can see equivalent to saying that they are P1s.
>>      
> Yes but in practice given the partial selections bug was only discovered
> in the middle of the release process (and I think we were effectively
> frozen), no consideration was given to a rating - we were only thinking
> of having set a date and getting close to it. I think what we are saying
> is that in that case we should have considered a rating and if it was
> P1 we stop the release and fix - irrespective of assumptions about
> when the next Beta might be.
>
>
>    
>> I don't agree about having a policy of 'at most 10 P2s outstanding'
>> or some such, because if we keep discovering P2s we never release.
>> Once we agree we have enough change to merit a release we should
>> agree a date.
>>      
> Good. Do we agree the date doesn't have to be the 1st of the month?
> But have we lost the impetus there for making changes, because we
> have no date until the changes are made? Is there some way of
> keeping the impetus going while sticking to "release when sufficient
> change"?
>
>
>    
>>> How many more Betas do we need
>>> and do users have patience for, before our final Beta? Can we target
>>> 1st April for final Beta? Can we target 1st April for clearing up the
>>> Windows P2s? Can we target 15th March for either, to save ourselves
>>> a couple of weeks?
>>>
>>>        
>> Very good questions, and ones that we may not like the answers to.
>> There is no question that getting to a stable release is a major
>> undertaking for us and not as fun as a "Let's add some cool new
>> features".  I do not actually mind if a stable Audacity is two years
>> away, if we are producing very good betas in the meantime, and if we can
>> develop the plug in system so that extensions can be added safely.
>>      
> In that case I feel on the download pages we'd pretty much have to
> explicitly point recent OS'es to Beta, and attempt some explanation of
> the content of Beta/Stable, as we were previously discussing. On
> that sort of timescale, I'd prefer a slightly dirty 2.0, I think.
>
>
>
> Gale
>