Re: [Audacity-devel] Plans for July

[Vaughan J. <va...@au...>]

Hear, hear.

And I think Martyn's RecordPauseOnSilence and PortBurn (if anybody has 
time to add it) are likewise great.

But, ever cautious, I'm thinking more so that we should have a 1.3.4 
before 1.4.0, to make sure it's all clean, even with the assumption that 
these are #ifdef-ed out.

Definitely, it's more fun to work on new stuff, and easy to justify 
adding incremental stuff, so I think we really need to decide on a "thus 
far, and no more" for 1.4.0...

Actually, I don't think it'd be horrible if there's a 1.5.x, if we agree 
that several incremental additions are not a 2.0 designation (which I 
think means major visible changes).

Of course, I'm about to go offline for a few days!

- V



Dominic Mazzoni wrote:
> James,
>
> I trust you to put an #ifdef guard around any code that could  
> potentially cause instability.  I'd say to go ahead and throw code  
> into CVS HEAD.
>
> Really exciting stuff!  I can't wait to see what you produce.
>
> - Dominic
>
> On Jun 29, 2007, at 4:24 PM, James Crook wrote:
>
>   
>> I'm taking this July off my paid work to work on Audacity with a brief
>> break from 9th to 13th for LSM 2007 in Amiens.  I've been planning  
>> this
>> for some time.
>>
>> By working full time on it, during July I'm expecting to get:
>>   - Theming completed.
>>   - External scripting progressed from 'proof of concept' to useful.
>>   - More facilities in place for GUI plug-ins.
>>   - Rivendell and Sonic Visualiser code in place and tested.
>>
>>
>> My strong preference is to be checking in code into CVS HEAD as I go.
>> I'd do it in such a way that the new functionality only appears in the
>> 'Debug wx284' builds.  I'd be using #ifdefs.  I don't think that many
>> #ifdefs will be needed.  The existing wxWidgets 2.6.x builds from CVS
>> HEAD would continue to have the same functionality as they do now, as
>> far as the user is concerned, and exactly the same strings for
>> translation, though they would gain any bug-fixes I make en-route.
>>
>> The alternative is to do this all on a branch.  I wouldn't do any real
>> bug fixes in that case, because I'd then have to work on two diverging
>> versions at the same time, possibly with different ways to fix the  
>> same
>> bugs on the different versions.  It also potentially creates a lot of
>> extra merging work downstream, especially if merging the two branches
>> together again has to wait some months.
>>
>> So what do active developers think?  Can I work on CVS HEAD or  
>> should I
>> develop on a branch during July?  My intention is to work on CVS HEAD
>> during July, unless one of the active developers gives that a  
>> veto.  It
>> just seems a lot more more efficient - particularly as I'll be able to
>> respond rapidly if there are problems.
>>
>> If you've any questions or need more details please ask.
>>
>> --James.
>>
>> ---------------------------------------------------------------------- 
>> ---
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> Audacity-devel mailing list
>> Aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>     
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Audacity-devel mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>
>