Thread: [Audacity-devel] call out for 2.0 release
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Vaughan J. <va...@au...> - 2012-01-20 05:57:23
|
We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). I believe we can review all the pending patches for lower priority bugs within a month (and decide which to apply). Can Audacity code translations and manual be ready in about the same time? If not, when? I am hoping for mid-February freeze, and a longer-than-recent review period, roughly 2 weeks, targeting a release of 2.0 on February 29 (emphasis on leap year!) Thanks, Vaughan |
From: David R. <d2...@gm...> - 2012-01-20 05:59:49
|
I noticed there's a little issue on Mac: When dragging an alias of a music file into Audacity, it does not redirect the alias to the music file, rather it says that files of this type (mp3, m4a, or whatever) are not supported. Is this worth filing a bug report for? Haven't gotten a chance to dig through the code yet. Not sure if it affects shortcuts in Windows too. Sorry if this is the wrong place to ask. --Dave On Jan 20, 2012, at 1:01 AM, Vaughan Johnson wrote: > We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). > > I believe we can review all the pending patches for lower priority bugs > within a month (and decide which to apply). > > Can Audacity code translations and manual be ready in about the same time? > > If not, when? > > I am hoping for mid-February freeze, and a longer-than-recent review > period, roughly 2 weeks, targeting a release of 2.0 on February 29 > (emphasis on leap year!) > > Thanks, > Vaughan > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Peter S. <pet...@ya...> - 2012-01-20 10:08:27
|
Hi Vaughan, Vaughan wrote: >Can Audacity ... manual be ready in about the same time? We had a big push on dealing with the outstanding P2s in the manual in December in the anticipation of a potentially impending 2.0 release (having followed the "chat" on the devel list and Bugzilla). Currently there are only two P2s remaining and they are both assigned and should be relatively simple and straightforward to fix. Peter. ________________________________ From: Vaughan Johnson <va...@au...> To: Audacity Developers List <aud...@li...>; audacity-quality <aud...@li...>; Audacity Translation List <aud...@li...> Sent: Friday, January 20, 2012 6:01 AM Subject: [Audacity-devel] call out for 2.0 release We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). I believe we can review all the pending patches for lower priority bugs within a month (and decide which to apply). Can Audacity code translations and manual be ready in about the same time? If not, when? I am hoping for mid-February freeze, and a longer-than-recent review period, roughly 2 weeks, targeting a release of 2.0 on February 29 (emphasis on leap year!) Thanks, Vaughan ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ audacity-devel mailing list aud...@li... https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Vaughan J. <va...@au...> - 2012-01-21 01:12:52
|
Thanks, Peter! - V On 1/20/2012 2:08 AM, Peter Sampson wrote: > Hi Vaughan, > > Vaughan wrote: >>Can Audacity ... manual be ready in about the same time? > > We had a big push on dealing with the outstanding P2s in the manual in > December in the anticipation of a potentially impending 2.0 release > (having followed the "chat" on the devel list and Bugzilla). > > Currently there are only two P2s remaining and they are both assigned > and should be relatively simple and straightforward to fix. > > Peter. > > > *From:* Vaughan Johnson <va...@au...> > *To:* Audacity Developers List <aud...@li...>; > audacity-quality <aud...@li...>; Audacity > Translation List <aud...@li...> > *Sent:* Friday, January 20, 2012 6:01 AM > *Subject:* [Audacity-devel] call out for 2.0 release > > We've finally vanquished all the P2 bugs in the code > (tinyurl.com/777ufhy <http://tinyurl.com/777ufhy>). > > I believe we can review all the pending patches for lower priority bugs > within a month (and decide which to apply). > > Can Audacity code translations and manual be ready in about the same time? > > If not, when? > > I am hoping for mid-February freeze, and a longer-than-recent review > period, roughly 2 weeks, targeting a release of 2.0 on February 29 > (emphasis on leap year!) > > Thanks, > Vaughan > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > audacity-devel mailing list > aud...@li... > <mailto:aud...@li...> > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > > > > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |
From: Benjamin D. <bd...@ub...> - 2012-01-20 17:21:56
Attachments:
signature.asc
|
Am Donnerstag, den 19.01.2012, 22:01 -0800 schrieb Vaughan Johnson: > We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). > > I believe we can review all the pending patches for lower priority bugs > within a month (and decide which to apply). > > Can Audacity code translations and manual be ready in about the same time? > > If not, when? > > I am hoping for mid-February freeze, and a longer-than-recent review > period, roughly 2 weeks, targeting a release of 2.0 on February 29 > (emphasis on leap year!) There are some bugs that I would like to see fixed before 2.0: * Audacity fails to build with latest FFmpeg/libav [1]. This should probably a P2 bug. Patches are attached and heavily tested. * Label is removed when deleting sound [2]. Patch attached. * failed to build against system sbsms [3]. Why do Audacity require a patched version of sbsms? [1] http://bugzilla.audacityteam.org/show_bug.cgi?id=467 [2] http://bugzilla.audacityteam.org/show_bug.cgi?id=466 [3] http://bugzilla.audacityteam.org/show_bug.cgi?id=288 -- Benjamin Drung Debian & Ubuntu Developer |
From: Gale (A. Team) <ga...@au...> - 2012-01-20 23:04:53
|
Benjamin wrote > Audacity fails to build with latest FFmpeg/libav [1]. This should > probably a P2 bug. Patches are attached and heavily tested. To add my vote, I made it a P3 for now. Win and Mac are OK. I'm happy with P2 or P3, though I'm still unclear what the problem was with committing it before now. If it wasn't safe then, I don't see how it can be safe now so close to 2.0. But I also asked questions in the bug report about export/import failures using FFmpeg inside Audacity. How bad are those? As a workaround, Linux users can always use FFmpeg (any version) standalone at the command-line, or with Audacity command-line exporter, can't they? > Label is removed when deleting sound [2]. Patch attached. It is a P4 enhancement IMO, that should be enabling either retention or deletion of labels, not preventing deletion. Gale > failed to build against system sbsms [3]. Why do Audacity require a > patched version > of sbsms? [1] http://bugzilla.audacityteam.org/show_bug.cgi?id=467 [2] http://bugzilla.audacityteam.org/show_bug.cgi?id=466 [3] http://bugzilla.audacityteam.org/show_bug.cgi?id=288 -- Benjamin Drung Debian & Ubuntu Developer -- View this message in context: http://audacity.238276.n2.nabble.com/call-out-for-2-0-release-tp7206510p7209492.html Sent from the audacity-devel mailing list archive at Nabble.com. |
From: Vaughan J. <va...@au...> - 2012-01-21 01:33:01
|
Thanks, Benjamin. I know that at least one of those has not been agreed to by QA, so I'm bring this back to that list. We now have the 'patch' keyword to help developers find these P3 or lower bugs that already have a patch. But is there any mechanism for easily discovering which patches are agreed to, i.e., without having to read the whole thread? - Vaughan On 1/20/2012 9:21 AM, Benjamin Drung wrote: > Am Donnerstag, den 19.01.2012, 22:01 -0800 schrieb Vaughan Johnson: >> We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). >> >> I believe we can review all the pending patches for lower priority bugs >> within a month (and decide which to apply). >> >> Can Audacity code translations and manual be ready in about the same time? >> >> If not, when? >> >> I am hoping for mid-February freeze, and a longer-than-recent review >> period, roughly 2 weeks, targeting a release of 2.0 on February 29 >> (emphasis on leap year!) > > There are some bugs that I would like to see fixed before 2.0: > > * Audacity fails to build with latest FFmpeg/libav [1]. This should > probably a P2 bug. Patches are attached and heavily tested. > > * Label is removed when deleting sound [2]. Patch attached. > > * failed to build against system sbsms [3]. Why do Audacity require a > patched version of sbsms? > > [1] http://bugzilla.audacityteam.org/show_bug.cgi?id=467 > [2] http://bugzilla.audacityteam.org/show_bug.cgi?id=466 > [3] http://bugzilla.audacityteam.org/show_bug.cgi?id=288 > > > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > > > > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Vaughan J. <va...@au...> - 2012-01-25 00:50:04
|
Does the lack of response on this mean there is no such way to easily see which patches have been agreed to, vs just being attached to a bugzilla entry? - V On 1/20/2012 5:36 PM, Vaughan Johnson wrote: > > We now have the 'patch' keyword to help developers find these P3 or > lower bugs that already have a patch. But is there any mechanism for > easily discovering which patches are agreed to, i.e., without having to > read the whole thread? > |
From: Michael C. <mc...@gm...> - 2012-01-21 08:49:15
|
On Fri, Jan 20, 2012 at 7:21 AM, Benjamin Drung <bd...@ub...> wrote: > Am Donnerstag, den 19.01.2012, 22:01 -0800 schrieb Vaughan Johnson: >> We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). >> >> I believe we can review all the pending patches for lower priority bugs >> within a month (and decide which to apply). >> >> Can Audacity code translations and manual be ready in about the same time? >> >> If not, when? >> >> I am hoping for mid-February freeze, and a longer-than-recent review >> period, roughly 2 weeks, targeting a release of 2.0 on February 29 >> (emphasis on leap year!) > > There are some bugs that I would like to see fixed before 2.0: > > * Audacity fails to build with latest FFmpeg/libav [1]. This should > probably a P2 bug. Patches are attached and heavily tested. > > * Label is removed when deleting sound [2]. Patch attached. > > * failed to build against system sbsms [3]. Why do Audacity require a > patched version of sbsms? I looked at the sbsms I get with 11.04 repositories and it seems to be version 1.7.0-1. The changelog in audacity svn says 2.0.2 (15 aug 2005). I know that some changes went into it after that as well that aren't in the changelog. Changelog has the line: Version 0.7.1 (2 Jul 2004) so I guess it's just too old or am I overlooking something? Michael |
From: Benjamin D. <bd...@ub...> - 2012-01-22 21:00:06
Attachments:
signature.asc
|
Am Freitag, den 20.01.2012, 22:48 -1000 schrieb Michael Chinen: > > * failed to build against system sbsms [3]. Why do Audacity require a > > patched version of sbsms? > > I looked at the sbsms I get with 11.04 repositories and it seems to be > version 1.7.0-1. > The changelog in audacity svn says 2.0.2 (15 aug 2005). Upstream didn't release a 2.0.2 source tarball. The latest version is 2.0.0 there. > I know that some changes went into it after that as well that aren't > in the changelog. > > Changelog has the line: Version 0.7.1 (2 Jul 2004) > so I guess it's just too old or am I overlooking something? I packaged libsbsms 2.0.0 (it will be in Ubuntu 12.04), but audacity fails to build with that version too. -- Benjamin Drung Debian & Ubuntu Developer |
From: Michael C. <mc...@gm...> - 2012-01-23 01:14:44
|
On Sun, Jan 22, 2012 at 10:59 AM, Benjamin Drung <bd...@ub...> wrote: > Am Freitag, den 20.01.2012, 22:48 -1000 schrieb Michael Chinen: >> > * failed to build against system sbsms [3]. Why do Audacity require a >> > patched version of sbsms? >> >> I looked at the sbsms I get with 11.04 repositories and it seems to be >> version 1.7.0-1. >> The changelog in audacity svn says 2.0.2 (15 aug 2005). > > Upstream didn't release a 2.0.2 source tarball. The latest version is > 2.0.0 there. In that case it seems sbsms upstream has not been updated for a very long time. When it was added to audacity I believe that was in 2008 by the Clayton (the author, who I'm cc'ing), which is 3 years after the 2.0.2, so our local changes could have a lot of modifications that were not added to the change logs. > >> I know that some changes went into it after that as well that aren't >> in the changelog. >> >> Changelog has the line: Version 0.7.1 (2 Jul 2004) >> so I guess it's just too old or am I overlooking something? > > I packaged libsbsms 2.0.0 (it will be in Ubuntu 12.04), but audacity > fails to build with that version too. I looked through our svn and found that the error you are getting (on bugzilla with rate0 and other struct vars) was a change made by Clayton, the author. So no need to worry about sending the patch upstream. So I guess we should probably force the local copy for now, since we can't really compare versions with our versionless local one. Michael |
From: Vaughan J. <va...@au...> - 2012-01-30 05:59:59
|
This is to confirm I am Release Manager for 2.0, per http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. Are we good for Feb 14 freeze on all fronts, and release on Feb 29? Thanks, Vaughan On 1/19/2012 10:01 PM, Vaughan Johnson wrote: > We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). > > I believe we can review all the pending patches for lower priority bugs > within a month (and decide which to apply). > > Can Audacity code translations and manual be ready in about the same time? > > If not, when? > > I am hoping for mid-February freeze, and a longer-than-recent review > period, roughly 2 weeks, targeting a release of 2.0 on February 29 > (emphasis on leap year!) > > Thanks, > Vaughan > > |
From: Martyn S. <mar...@gm...> - 2012-01-31 01:22:43
|
Looking good to go here! Martyn On 30/01/2012 06:03, Vaughan Johnson wrote: > This is to confirm I am Release Manager for 2.0, per > http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. > > Are we good for Feb 14 freeze on all fronts, and release on Feb 29? > > Thanks, > Vaughan > > > On 1/19/2012 10:01 PM, Vaughan Johnson wrote: >> We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). >> >> I believe we can review all the pending patches for lower priority bugs >> within a month (and decide which to apply). >> >> Can Audacity code translations and manual be ready in about the same time? >> >> If not, when? >> >> I am hoping for mid-February freeze, and a longer-than-recent review >> period, roughly 2 weeks, targeting a release of 2.0 on February 29 >> (emphasis on leap year!) >> >> Thanks, >> Vaughan >> >> > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Audacity-quality mailing list > Aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-quality |
From: Vaughan J. <va...@au...> - 2012-02-02 00:01:39
|
On 1/31/2012 5:04 PM, Michael Chinen wrote: > On Mon, Jan 30, 2012 at 3:22 PM, Martyn Shaw <mar...@gm...> wrote: >> Looking good to go here! >> >> Martyn >> >> On 30/01/2012 06:03, Vaughan Johnson wrote: >>> This is to confirm I am Release Manager for 2.0, per >>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. >>> >>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? > > I can do the linux tarballs again. > I can also do mac if no one responds by the 7th. Excellent. Thanks, Michael. Anybody up for Windows builds? - V |
From: Vaughan J. <va...@au...> - 2012-02-09 05:35:47
|
All still good for freeze on Feb 14 and release on Feb 29? I think so. Silence is consent! Thanks, Vaughan On 1/29/2012 10:03 PM, Vaughan Johnson wrote: > This is to confirm I am Release Manager for 2.0, per > http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. > > Are we good for Feb 14 freeze on all fronts, and release on Feb 29? > > Thanks, > Vaughan > > > On 1/19/2012 10:01 PM, Vaughan Johnson wrote: >> We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). >> >> I believe we can review all the pending patches for lower priority bugs >> within a month (and decide which to apply). >> >> Can Audacity code translations and manual be ready in about the same time? >> >> If not, when? >> >> I am hoping for mid-February freeze, and a longer-than-recent review >> period, roughly 2 weeks, targeting a release of 2.0 on February 29 >> (emphasis on leap year!) >> >> Thanks, >> Vaughan >> >> > |
From: Bill W. <bi...@go...> - 2012-02-09 16:28:32
|
On 09/02/2012, at 12:39 AM, Vaughan Johnson wrote: > All still good for freeze on Feb 14 and release on Feb 29? I think so. > > Silence is consent! The manual contains two borderline P2s. http://manual.audacityteam.org/man/User:PeterSampson/Outstanding_P2s_(To-Do-2s)_in_the_manual These will be cleared one way or another (either by completing the work or reaching consensus that they can be downgraded) before Feb 14. -- Bill > > Thanks, > Vaughan > > > On 1/29/2012 10:03 PM, Vaughan Johnson wrote: >> This is to confirm I am Release Manager for 2.0, per >> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. >> >> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? >> >> Thanks, >> Vaughan >> >> >> On 1/19/2012 10:01 PM, Vaughan Johnson wrote: >>> We've finally vanquished all the P2 bugs in the code (tinyurl.com/777ufhy). >>> >>> I believe we can review all the pending patches for lower priority bugs >>> within a month (and decide which to apply). >>> >>> Can Audacity code translations and manual be ready in about the same time? >>> >>> If not, when? >>> >>> I am hoping for mid-February freeze, and a longer-than-recent review >>> period, roughly 2 weeks, targeting a release of 2.0 on February 29 >>> (emphasis on leap year!) >>> >>> Thanks, >>> Vaughan >>> >>> >> > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
From: Vaughan J. <va...@au...> - 2012-02-09 23:39:39
|
Thanks, Bill. Please keep me posted. - V On 2/9/2012 8:28 AM, Bill Wharrie wrote: > > On 09/02/2012, at 12:39 AM, Vaughan Johnson wrote: > >> All still good for freeze on Feb 14 and release on Feb 29? I think so. >> >> Silence is consent! > > The manual contains two borderline P2s. > > http://manual.audacityteam.org/man/User:PeterSampson/Outstanding_P2s_(To-Do-2s)_in_the_manual > > These will be cleared one way or another (either by completing the work or reaching consensus that they can be downgraded) before Feb 14. > > -- Bill > >> >> Thanks, >> Vaughan >> >>[...] |
From: Bill W. <bi...@go...> - 2012-02-12 16:59:10
|
What time on Feb 14 is the freeze? 23:59 GMT? -- Bill >> >> On 1/29/2012 10:03 PM, Vaughan Johnson wrote: >>> This is to confirm I am Release Manager for 2.0, per >>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. >>> >>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? >>> >>> Thanks, >>> Vaughan >>> |
From: Vaughan J. <va...@au...> - 2012-02-13 17:58:01
|
Let's make it 21:00 GMT/UTC, so Martyn doesn't have to stay up so late. But I'm open to alternatives. - V On 2/12/2012 8:59 AM, Bill Wharrie wrote: > What time on Feb 14 is the freeze? 23:59 GMT? > > -- Bill > >>> >>> On 1/29/2012 10:03 PM, Vaughan Johnson wrote: >>>> This is to confirm I am Release Manager for 2.0, per >>>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. >>>> >>>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? >>>> >>>> Thanks, >>>> Vaughan >>>> > > |
From: Gale (A. Team) <ga...@au...> - 2012-02-13 23:36:34
|
"Vaughan Johnson" wrote: > Let's make it 21:00 GMT/UTC, so Martyn doesn't have to stay up so late. > But I'm open to alternatives. I haven't volunteered for anything yet as I've been more than usually poorly since the 1st and I was told to volunteer for less. Am a little better ATM. I think we have everything except Win ANSI build which is for me to do, and README. I haven't started that -does anyone else want to do it? I'm fine with that if so. What's in it - * fixes/improvements since 1.3.14 * Confirmation that the bugs listed in "1.2 Release Notes": http://audacity.sourceforge.net/download/release-notes have been fixed (except MIDI) * Potted summary of new / improved features since 1.2.6 ? Or some other plan? If I'm to do that, the later the better. Is 22:30 GMT or so reasonable? Otherwise I'll deal with http://wiki.audacityteam.org/wiki/Release_Process#Process #9 (upload zipped manual) and http://wiki.audacityteam.org/wiki/Release_Process#Release_Announcements # 2 - 7 only (but I will deal with http://audacity.sourceforge.net/help/faq). I'll post separately about FAQ's to -quality. Gale On 2/12/2012 8:59 AM, Bill Wharrie wrote: > What time on Feb 14 is the freeze? 23:59 GMT? > > -- Bill > >>> >>> On 1/29/2012 10:03 PM, Vaughan Johnson wrote: >>>> This is to confirm I am Release Manager for 2.0, per >>>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. >>>> >>>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? >>>> >>>> Thanks, >>>> Vaughan -- View this message in context: http://audacity.238276.n2.nabble.com/call-out-for-2-0-release-tp7206510p7282412.html Sent from the audacity-devel mailing list archive at Nabble.com. |
From: Vaughan J. <va...@au...> - 2012-02-14 07:56:36
|
Gale, sorry to hear you're not well. 22:30 GMT is fine, or we can postpone another 24 hours to Feb 15, and still have plenty of time to be ready to release on Feb 29 (still two weeks after). I think we're looking good for that. I'll do the README if needed. Thanks, all best, Vaughan On 2/13/2012 3:36 PM, Gale (Audacity Team) wrote: > "Vaughan Johnson" wrote: >> Let's make it 21:00 GMT/UTC, so Martyn doesn't have to stay up so late. >> But I'm open to alternatives. > > I haven't volunteered for anything yet as I've been more than usually poorly > since > the 1st and I was told to volunteer for less. Am a little better ATM. > > I think we have everything except Win ANSI build which is for me to do, and > README. > I haven't started that -does anyone else want to do it? I'm fine with that > if so. > > What's in it - > > * fixes/improvements since 1.3.14 > * Confirmation that the bugs listed in "1.2 Release Notes": > http://audacity.sourceforge.net/download/release-notes > > have been fixed (except MIDI) > * Potted summary of new / improved features since 1.2.6 ? > > Or some other plan? If I'm to do that, the later the better. Is 22:30 GMT or > so reasonable? > > Otherwise I'll deal with > http://wiki.audacityteam.org/wiki/Release_Process#Process > #9 (upload zipped manual) > > and > http://wiki.audacityteam.org/wiki/Release_Process#Release_Announcements > # 2 - 7 only (but I will deal with > http://audacity.sourceforge.net/help/faq). > > I'll post separately about FAQ's to -quality. > > > > > > Gale > > > On 2/12/2012 8:59 AM, Bill Wharrie wrote: >> What time on Feb 14 is the freeze? 23:59 GMT? >> >> -- Bill >> >>>> >>>> On 1/29/2012 10:03 PM, Vaughan Johnson wrote: >>>>> This is to confirm I am Release Manager for 2.0, per >>>>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. >>>>> >>>>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? >>>>> >>>>> Thanks, >>>>> Vaughan > |
From: Gale A. <ga...@au...> - 2012-02-14 17:36:37
|
| From Vaughan Johnson <va...@au...> | Tue, 14 Feb 2012 00:00:36 -0800 | Subject: [Audacity-devel] RM , and schedule for 2.0 release > Gale, sorry to hear you're not well. > > 22:30 GMT is fine, or we can postpone another 24 hours to Feb 15, and > still have plenty of time to be ready to release on Feb 29 (still two > weeks after). > > I think we're looking good for that. I'll do the README if needed. > > Thanks, all best, > Vaughan Thanks, Vaughan. I'll start looking at the README now; as you haven't commented on content I assume what I suggested was OK. Even if I finish that README today I think Feb 15th would be better anyway because of the committed fixes for: http://bugzilla.audacityteam.org/show_bug.cgi?id=334 http://bugzilla.audacityteam.org/show_bug.cgi?id=44 which are crash-risk so must be given a fair test. And clearly all the commits made won't be RESOLVED-FIXED by tonight (though most wouldn't affect the README). @Bill, the bug 334 commit should be in the "Feb 14th 2012 03:15 GMT" Nightly. Gale > On 2/13/2012 3:36 PM, Gale (Audacity Team) wrote: > > "Vaughan Johnson" wrote: > >> Let's make it 21:00 GMT/UTC, so Martyn doesn't have to stay up so late. > >> But I'm open to alternatives. > > > > I haven't volunteered for anything yet as I've been more than usually poorly > > since > > the 1st and I was told to volunteer for less. Am a little better ATM. > > > > I think we have everything except Win ANSI build which is for me to do, and > > README. > > I haven't started that -does anyone else want to do it? I'm fine with that > > if so. > > > > What's in it - > > > > * fixes/improvements since 1.3.14 > > * Confirmation that the bugs listed in "1.2 Release Notes": > > http://audacity.sourceforge.net/download/release-notes > > > > have been fixed (except MIDI) > > * Potted summary of new / improved features since 1.2.6 ? > > > > Or some other plan? If I'm to do that, the later the better. Is 22:30 GMT or > > so reasonable? > > > > Otherwise I'll deal with > > http://wiki.audacityteam.org/wiki/Release_Process#Process > > #9 (upload zipped manual) > > > > and > > http://wiki.audacityteam.org/wiki/Release_Process#Release_Announcements > > # 2 - 7 only (but I will deal with > > http://audacity.sourceforge.net/help/faq). > > > > I'll post separately about FAQ's to -quality. > > > > > > > > > > > > Gale > > > > > > On 2/12/2012 8:59 AM, Bill Wharrie wrote: > >> What time on Feb 14 is the freeze? 23:59 GMT? > >> > >> -- Bill > >> > >>>> > >>>> On 1/29/2012 10:03 PM, Vaughan Johnson wrote: > >>>>> This is to confirm I am Release Manager for 2.0, per > >>>>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. > >>>>> > >>>>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? > >>>>> > >>>>> Thanks, > >>>>> Vaughan |
From: Vaughan J. <va...@au...> - 2012-02-14 19:46:52
|
On 2/14/2012 9:36 AM, Gale Andrews wrote: > > | From Vaughan Johnson <va...@au...> > | Tue, 14 Feb 2012 00:00:36 -0800 > | Subject: [Audacity-devel] RM , and schedule for 2.0 release >> Gale, sorry to hear you're not well. >> >> 22:30 GMT is fine, or we can postpone another 24 hours to Feb 15, and >> still have plenty of time to be ready to release on Feb 29 (still two >> weeks after). >> >> I think we're looking good for that. I'll do the README if needed. >> >> Thanks, all best, >> Vaughan > > Thanks, Vaughan. > > I'll start looking at the README now; as you haven't commented on > content I assume what I suggested was OK. That's fine. Better that it has the consistency of you doing it again. Thanks. > > Even if I finish that README today I think Feb 15th would be better > anyway because of the committed fixes for: > http://bugzilla.audacityteam.org/show_bug.cgi?id=334 > http://bugzilla.audacityteam.org/show_bug.cgi?id=44 > > which are crash-risk so must be given a fair test. And clearly all the > commits made won't be RESOLVED-FIXED by tonight (though most > wouldn't affect the README). > > @Bill, the bug 334 commit should be in the "Feb 14th 2012 03:15 GMT" > Nightly. Okay, I'll review those again. Freeze is now officially set for 21:00 GMT on Feb 15. Having all the P2's RESOLVED-FIXED is a reasonable requirement for freeze, but not necessarily for P3's. I went ahead and did http://wiki.audacityteam.org/wiki/Release_Process#Process step 6.1 - Vaughan > > > > > Gale > > >> On 2/13/2012 3:36 PM, Gale (Audacity Team) wrote: >>> "Vaughan Johnson" wrote: >>>> Let's make it 21:00 GMT/UTC, so Martyn doesn't have to stay up so late. >>>> But I'm open to alternatives. >>> >>> I haven't volunteered for anything yet as I've been more than usually poorly >>> since >>> the 1st and I was told to volunteer for less. Am a little better ATM. >>> >>> I think we have everything except Win ANSI build which is for me to do, and >>> README. >>> I haven't started that -does anyone else want to do it? I'm fine with that >>> if so. >>> >>> What's in it - >>> >>> * fixes/improvements since 1.3.14 >>> * Confirmation that the bugs listed in "1.2 Release Notes": >>> http://audacity.sourceforge.net/download/release-notes >>> >>> have been fixed (except MIDI) >>> * Potted summary of new / improved features since 1.2.6 ? >>> >>> Or some other plan? If I'm to do that, the later the better. Is 22:30 GMT or >>> so reasonable? >>> >>> Otherwise I'll deal with >>> http://wiki.audacityteam.org/wiki/Release_Process#Process >>> #9 (upload zipped manual) >>> >>> and >>> http://wiki.audacityteam.org/wiki/Release_Process#Release_Announcements >>> # 2 - 7 only (but I will deal with >>> http://audacity.sourceforge.net/help/faq). >>> >>> I'll post separately about FAQ's to -quality. >>> >>> >>> >>> >>> >>> Gale >>> >>> >>> On 2/12/2012 8:59 AM, Bill Wharrie wrote: >>>> What time on Feb 14 is the freeze? 23:59 GMT? >>>> >>>> -- Bill >>>> >>>>>> >>>>>> On 1/29/2012 10:03 PM, Vaughan Johnson wrote: >>>>>>> This is to confirm I am Release Manager for 2.0, per >>>>>>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. >>>>>>> >>>>>>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? >>>>>>> >>>>>>> Thanks, >>>>>>> Vaughan > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: Vaughan J. <vau...@sb...> - 2012-02-14 19:51:31
|
Announcement: Due to unforeseen issues, we are delaying the freeze for 2.0 by one day, so it will be 21:00 GMT on Feb 15. Thanks, Vaughan -------- Original Message -------- Subject: Re: [Audacity-devel] RM , and schedule for 2.0 release Date: Tue, 14 Feb 2012 11:50:53 -0800 From: Vaughan Johnson <va...@au...> To: aud...@li... On 2/14/2012 9:36 AM, Gale Andrews wrote: > > | From Vaughan Johnson <va...@au...> > | Tue, 14 Feb 2012 00:00:36 -0800 > | Subject: [Audacity-devel] RM , and schedule for 2.0 release >> Gale, sorry to hear you're not well. >> >> 22:30 GMT is fine, or we can postpone another 24 hours to Feb 15, and >> still have plenty of time to be ready to release on Feb 29 (still two >> weeks after). >> >> I think we're looking good for that. I'll do the README if needed. >> >> Thanks, all best, >> Vaughan > > Thanks, Vaughan. > > I'll start looking at the README now; as you haven't commented on > content I assume what I suggested was OK. That's fine. Better that it has the consistency of you doing it again. Thanks. > > Even if I finish that README today I think Feb 15th would be better > anyway because of the committed fixes for: > http://bugzilla.audacityteam.org/show_bug.cgi?id=334 > http://bugzilla.audacityteam.org/show_bug.cgi?id=44 > > which are crash-risk so must be given a fair test. And clearly all the > commits made won't be RESOLVED-FIXED by tonight (though most > wouldn't affect the README). > > @Bill, the bug 334 commit should be in the "Feb 14th 2012 03:15 GMT" > Nightly. Okay, I'll review those again. Freeze is now officially set for 21:00 GMT on Feb 15. Having all the P2's RESOLVED-FIXED is a reasonable requirement for freeze, but not necessarily for P3's. I went ahead and did http://wiki.audacityteam.org/wiki/Release_Process#Process step 6.1 - Vaughan > > > > > Gale > > >> On 2/13/2012 3:36 PM, Gale (Audacity Team) wrote: >>> "Vaughan Johnson" wrote: >>>> Let's make it 21:00 GMT/UTC, so Martyn doesn't have to stay up so late. >>>> But I'm open to alternatives. >>> >>> I haven't volunteered for anything yet as I've been more than usually poorly >>> since >>> the 1st and I was told to volunteer for less. Am a little better ATM. >>> >>> I think we have everything except Win ANSI build which is for me to do, and >>> README. >>> I haven't started that -does anyone else want to do it? I'm fine with that >>> if so. >>> >>> What's in it - >>> >>> * fixes/improvements since 1.3.14 >>> * Confirmation that the bugs listed in "1.2 Release Notes": >>> http://audacity.sourceforge.net/download/release-notes >>> >>> have been fixed (except MIDI) >>> * Potted summary of new / improved features since 1.2.6 ? >>> >>> Or some other plan? If I'm to do that, the later the better. Is 22:30 GMT or >>> so reasonable? >>> >>> Otherwise I'll deal with >>> http://wiki.audacityteam.org/wiki/Release_Process#Process >>> #9 (upload zipped manual) >>> >>> and >>> http://wiki.audacityteam.org/wiki/Release_Process#Release_Announcements >>> # 2 - 7 only (but I will deal with >>> http://audacity.sourceforge.net/help/faq). >>> >>> I'll post separately about FAQ's to -quality. >>> >>> >>> >>> >>> >>> Gale >>> >>> >>> On 2/12/2012 8:59 AM, Bill Wharrie wrote: >>>> What time on Feb 14 is the freeze? 23:59 GMT? >>>> >>>> -- Bill >>>> >>>>>> >>>>>> On 1/29/2012 10:03 PM, Vaughan Johnson wrote: >>>>>>> This is to confirm I am Release Manager for 2.0, per >>>>>>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. >>>>>>> >>>>>>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? >>>>>>> >>>>>>> Thanks, >>>>>>> Vaughan > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
From: Gale A. <ga...@au...> - 2012-02-14 22:31:23
|
| From Vaughan Johnson <va...@au...> | Tue, 14 Feb 2012 11:50:53 -0800 | Subject: [Audacity-devel] RM , and schedule for 2.0 release > > On 2/14/2012 9:36 AM, Gale Andrews wrote: > > > > | From Vaughan Johnson <va...@au...> > > | Tue, 14 Feb 2012 00:00:36 -0800 > > | Subject: [Audacity-devel] RM , and schedule for 2.0 release > >> Gale, sorry to hear you're not well. > >> > >> 22:30 GMT is fine, or we can postpone another 24 hours to Feb 15, and > >> still have plenty of time to be ready to release on Feb 29 (still two > >> weeks after). > >> > >> I think we're looking good for that. I'll do the README if needed. > >> > >> Thanks, all best, > >> Vaughan > > > > Thanks, Vaughan. > > > > I'll start looking at the README now; as you haven't commented on > > content I assume what I suggested was OK. > > That's fine. Better that it has the consistency of you doing it again. OK. README is essentially done except for: * any P3's which may get RESOLVED-FIXED (or identified) between now and freeze * "Potted summary" of new / improved features since 1.2.6. Question about potted summary. There will be many new features in 2.0.0 compared to 1.2.6. Can I assume we're OK with summarising the "new features" into five bullet points (or less), which might then be short enough for re-use in the release announcement? My idea was we could then link to an updated: http://audacity.sourceforge.net/about/features for the meat. We could even "star" items on there as "new in 2.0.0". > > Even if I finish that README today I think Feb 15th would be better > > anyway because of the committed fixes for: > > http://bugzilla.audacityteam.org/show_bug.cgi?id=334 > > http://bugzilla.audacityteam.org/show_bug.cgi?id=44 > > > > which are crash-risk so must be given a fair test. And clearly all the > > commits made won't be RESOLVED-FIXED by tonight (though most > > wouldn't affect the README). > > > > @Bill, the bug 334 commit should be in the "Feb 14th 2012 03:15 GMT" > > Nightly. > > Okay, I'll review those again. Freeze is now officially set for 21:00 > GMT on Feb 15. Thanks. That will help. > Having all the P2's RESOLVED-FIXED is a reasonable requirement for > freeze, but not necessarily for P3's. All (listed) P2's are RESOLVED-FIXED already. I have plenty do to on P3 or below DEVEL-FIXED's, but if I do less for release on the SF main site I should have a bit more time to work on bugs. Gale > >> On 2/13/2012 3:36 PM, Gale (Audacity Team) wrote: > >>> "Vaughan Johnson" wrote: > >>>> Let's make it 21:00 GMT/UTC, so Martyn doesn't have to stay up so late. > >>>> But I'm open to alternatives. > >>> > >>> I haven't volunteered for anything yet as I've been more than usually poorly > >>> since > >>> the 1st and I was told to volunteer for less. Am a little better ATM. > >>> > >>> I think we have everything except Win ANSI build which is for me to do, and > >>> README. > >>> I haven't started that -does anyone else want to do it? I'm fine with that > >>> if so. > >>> > >>> What's in it - > >>> > >>> * fixes/improvements since 1.3.14 > >>> * Confirmation that the bugs listed in "1.2 Release Notes": > >>> http://audacity.sourceforge.net/download/release-notes > >>> > >>> have been fixed (except MIDI) > >>> * Potted summary of new / improved features since 1.2.6 ? > >>> > >>> Or some other plan? If I'm to do that, the later the better. Is 22:30 GMT or > >>> so reasonable? > >>> > >>> Otherwise I'll deal with > >>> http://wiki.audacityteam.org/wiki/Release_Process#Process > >>> #9 (upload zipped manual) > >>> > >>> and > >>> http://wiki.audacityteam.org/wiki/Release_Process#Release_Announcements > >>> # 2 - 7 only (but I will deal with > >>> http://audacity.sourceforge.net/help/faq). > >>> > >>> I'll post separately about FAQ's to -quality. > >>> > >>> > >>> > >>> > >>> > >>> Gale > >>> > >>> > >>> On 2/12/2012 8:59 AM, Bill Wharrie wrote: > >>>> What time on Feb 14 is the freeze? 23:59 GMT? > >>>> > >>>> -- Bill > >>>> > >>>>>> > >>>>>> On 1/29/2012 10:03 PM, Vaughan Johnson wrote: > >>>>>>> This is to confirm I am Release Manager for 2.0, per > >>>>>>> http://wiki.audacityteam.org/wiki/Release_Process#Process, step 2. > >>>>>>> > >>>>>>> Are we good for Feb 14 freeze on all fronts, and release on Feb 29? > >>>>>>> > >>>>>>> Thanks, > >>>>>>> Vaughan |