Re: [Audacity-devel] Double freeze over.

[Gale A. <ga...@au...>]

| From James Crook <cr...@in...> 
| Tue, 02 Mar 2010 13:02:35 +0000
| Subject: [Audacity-devel] Double freeze over.
> We're already past the intended 1st March release.  I'm allergic to 
> pushing dates out in small little steps, so this release cycle is hereby 
> pulled.  We're out of double freeze now.
> 
> Al's solution to dll-hell needs more discussion and investigation for sure.
> Koz's import-crash is on a mac.  Gale says it's a P2, so P2 it is.
> 
> I don't think this is a bad result at all.  The release attempt has been 
> a kind of pipe-cleaning.  Al and Peter, are you enthusiastic to do the 
> builds for the1.3.12 release for April in due course?  If so, I will 
> again volunteer as release manager and we will go around again, this 
> time trying for 2nd April.

Is there a difference between "release manager" and "release 
co-ordinator", which was the term we used when the freeze started 
on the 22nd?  

When I suggested the person calling the freeze should co-ordinate
the release, I was thinking of making sure all platforms have the 
same content, files are uploaded to the right place with correct file
name etc. We weren't anticipating a problem then, but if it comes to
having to make quality judgements about whether to release, that's
a different issue, and maybe should be more of a consensus thing? 

I do think: 
http://wiki.audacityteam.org/wiki/Release_Process

should make these ambiguities clear. 

Who's Peter -  Paul?  

I would defer on your view that this isn't a bad result and remain 
opposed to cancelling releases because they are a few days behind
some arbitrary date that was decided. I think that makes us look 
silly, given we've had (even in a limited way) to make a proposed
release date public. Plus, doesn't it essentially push a major release
back a few weeks every time it happens? 



Thanks



Gale