Re: [Audacity-devel] Release often; 1st Jan/1st Feb
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Richard A. <ri...@au...> - 2009-12-05 23:00:18
|
On Fri, 2009-12-04 at 14:59 +0000, James Crook wrote: > As I understand it we will be doing another beta release on 1st > January. Releasing to a time schedule definitely has been good this > time round. +1 My availability from now until Christmas is pretty limitted, but I don't think we have any P3 or higher Linux-specific bugs that have to be addressed. After Christmas day itself I should have a few days to start rolling source tarballs and so on in the run up to 1st Jan and a few days after that before I start work. > Suggestions: > > We are in a good state with *translations*. I suggest we do not solicit > another round of translations for the 1st Jan release, but do after that > if it is looking like we're on target for a stable release. We should publicise this decision to translators if we agree it, so that they don't feel they have been left out of 1.3.11 release, but yes, this is a reasonable stance to take. > *GSoC 2010* Do we plan to participate? If so we should be thinking > about it now and doing some planning. Hmm, it would be nice to be able to polish up some from http://wiki.audacityteam.org/index.php?title=More_GSoC_Ideas to add to the list, but I don't know whether I am in a position to mentor or not, and probably won't in time - I expect to be very busy off-line through the next 4 months or so, but that could suddenly disappear at any moment. So it's unlikely I can commit to mentoring this year, unfortunately. > Are we in *string freeze* between now and Jan? I am fairly sure that we > are not, but would like to see we are all on the same page on this. No, I'm sure we aren't, although we still have a presumption against gratuitous string changes as we work up to stable, for the sake of the Manual people. > Are we good with continuing to not release *experimental features* in > these betas? I think we are. I think we should not switch on label > linking or theme preferences again until we have the P2s cleared. I think we shouldn't switch on anything currently disabled until we release a stable version. Only then can we consider anything new. > Are we good with allowing experimental features, e.g. perhaps context > sensitive help for preferences, to be added but left disabled except in > nightlies during this time? No reason not if they (relatively) cleanly disable. > Are we good with adding more hooks for > plug-ins (transparent to normal users)? I think we are to both, but I > want to confirm this. Yes, this is user-transparent (so won't affect Manual) and should have no operational effects when they aren't used. > Re-organisation of *menus*. Split thread. Richard |