Re: [Audacity-devel] [Audacity-quality] final decision on releasing rc3 as 1.3.13 final
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Vaughan J. <va...@au...> - 2011-04-10 20:53:05
|
On 4/10/2011 1:20 PM, Vaughan Johnson wrote: > Thanks, Bill. I don't see those as warranting another rc, and another 48 > hour cycle. > > And this may not be the best time, but I want to address the > equivocation about the initial deadline. That is, a few people voiced > the opinion that it doesn't matter if we don't complete the release > cycle quickly, and miss the deadline we set for release, and miss it > again for a long series of rc cycles. > > Two points: > > * If we do freezes as I indicated, and as we were supposed to do this > time (as I am RM), everybody is held up from doing any Audacity work > other than fixing release blocks. The quicker we complete the release, > the sooner we can get back to productivity that's not just about > completing the release. > > * I have lots of other things to do, and being RM took up a lot of my > time for more than a week. My clients have been clamoring for me to get > back to their projects, but it was important to me to get this release > out. This actually interfered with me making a living. I think that's > true of several team members. Some team members may not have to worry > about that, but I think they should be considerate of those who do. One more thing about this. Even if some of you are not concerned about others of us needing to make a living, let's not lose sight of the fact that *every* volunteer hour spent on Audacity has value. Choosing how to spend those hours is a matter of budgeting. Even if we decided to throw in fixes for these last minute niggles about the manual, and the people willing to do that work on the manual have copious time and don't care, consider that we're then spending a few hours of the builders' time, too, and yes really do need to also spend more hours testing the rc. (I say 48, every time, especially as we're spread out around the globe.) Really, doing builds (drudge work) should be considered more expensive to Audacity project than hours spent developing cool new features (fun work). People volunteer much more readily to do fun work, and if drudge becomes dominant, it really damps morale, and reduces our asset pool of hours going forward. Let's think of the real expense to the Audacity project of doing yet another rc and delaying release again -- it's quite considerable. Thanks, Vaughan |