Re: [Audacity-quality] final decision on releasing rc3 as 1.3.13 final

[Martyn S. <mar...@gm...>]

On 10/04/2011 22:56, Vaughan Johnson wrote:
> Thanks, Martyn. I think I missed your hour because I was just on the
> phone with a client for about an hour!
>
> We're at http://wiki.audacityteam.org/wiki/Release_Process#Process step
> 8 and onward:
>
> 8. Can we just rename on GoogleCode without deleting/uploading?

I couldn't see how to do that so I just downloaded, re-uploaded, 
checked that the SHA1 Checksum was the same and then deleted the rc3. 
  Only did the win unicode exe and zip though.

> 9. Volunteer?

I could have done that but don't know how.  Sorry.

TTFN
Martyn

> 10. Gale, I think this is typically yours. Up for it?
>
> 11 - 13. I'll do these when we're set.
>
>
> Thanks,
> Vaughan
>
>
> On 4/10/2011 2:04 PM, Martyn Shaw wrote:
>> Good call, RM!
>>
>> Anything I can do to help finish the job?  I have about an hour.
>>
>> Martyn
>>
>> On 10/04/2011 21:37, Vaughan Johnson wrote:
>>> Summary: I have read the subsequent messages from Leland (positive
>>> testing results) and Bill (remaining issues in the manual) in this
>>> thread, and I see nothing remaining as being release blocking.
>>>
>>> *Let's release 1.3.13 based on rc3, ASAP!* That is by fiat from RM.
>>>
>>> We should announce it by 19:00 UTC on April 11.
>>>
>>>
>>>
>>> On 4/10/2011 11:20 AM, Gale Andrews wrote:
>>>>
>>>> | From Vaughan Johnson<va...@au...>
>>>> |<snip>
>>>>>
>>>>> It's only a little less than 24 hours, so I propose we decide by 19:00
>>>>> UTC on April 10. If no objections by then (that RM thinks warrant
>>>>> stoppage), we'll release 1.3.13.
>>>>>
>>> <snip>
>>>> If you think the mismatch between the manifest and the dll's is less of a
>>>> risk than having the older dll's,
>>>
>>> I already said that, yes. Please don't bring up issues that have been
>>> decided.
>>>
>>>
>>>> then my only concern is still with the
>>>> Manual in rc3:
>>>>
>>>> 1 It's slightly different between the platforms
>>>
>>> If we did the freezes properly, that would not be the case. But at this
>>> point I don't see any manual issues as release blocking. We all know
>>> there's lots of work to be done on the manual.
>>>
>>>
>>>>
>>>> 2 the Preferences images are all incorrect (and the content
>>>>      of the Preferences pages is in some cases incorrect)
>>>>
>>>> 3 no account at all has been taken of the new behaviour
>>>>      and dialogue when importing uncompressed files. So it's
>>>>      wrong as well as incomplete.
>>>>
>>>> If we pulled the Manual now and rebuilt we would fix 1) and 3)
>>>> on the basis of work done since rc3, and  2) would be improved.
>>>>
>>>> I don't think it would take more than a couple of hours to fix 2)
>>>> properly. I'm sure you would have volunteers.
>>>>
>>>> 3) is the most important to me, and likely to cause the most issue.
>>>> I would be glad to rebuild to fix that.
>>>
>>> Still, I do not think release blocking.
>>>
>>>
>>>> Would it really need
>>>> another 48 hour test?
>>>
>>> Yes, absolutely. I have been VERY clear about that, so I am disappointed
>>> you are asking.
>>>
>>> Say we didn't do that and somebody made a major mistake in building rc4
>>> (it happens!), and Audacity would crash on launch, but we just posted it
>>> as final release immediately. Then we'd have to do a hot fix, against
>>> policy. NOT ON.
>>>
>>> If we do an rc4, builders need to go through the process again. For just
>>> one of the builders, Martyn, that's an hour of his time that would be
>>> far better spent elsewhere on Audacity, imo.
>>>
>>> And then the rc4 would need to go through full testing, at least be
>>> installed and launched and run through some paces on all platforms.
>>> We've already had that opportunity on rc3. Let's not require it again
>>> for an rc4 just because of these last minute niggles.
>>>
>>> The point of having that rule is to not have to discuss every time
>>> whether we really need another 48 hour cycle, and to keep us focused on
>>> what is really release blocking. The rc3 has been posted for>   3 days.
>>> Let's release it.
>>>
>>> Thanks,
>>> Vaughan
>>>
>>> ------------------------------------------------------------------------------
>>> Xperia(TM) PLAY
>>> It's a major breakthrough. An authentic gaming
>>> smartphone on the nation's most reliable network.
>>> And it wants your games.
>>> http://p.sf.net/sfu/verizon-sfdev
>>> _______________________________________________
>>> Audacity-quality mailing list
>>> Aud...@li...
>>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
>> ------------------------------------------------------------------------------
>> Xperia(TM) PLAY
>> It's a major breakthrough. An authentic gaming
>> smartphone on the nation's most reliable network.
>> And it wants your games.
>> http://p.sf.net/sfu/verizon-sfdev
>> _______________________________________________
>> Audacity-quality mailing list
>> Aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-quality
>>
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> Audacity-quality mailing list
> Aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-quality