Gale your memory is correct.  On 3rd June I said:
I would like to make the news item a little more human and interacting / relating honestly with the audience; less like a corporation puffing their wares; so rather than

"The Audacity Team is elated to announce"

"The Audacity Team is exhausted, but delighted to announce"

I realise now that part of it is a language thing.  Words have slightly different nuance in the US than in the UK/Ireland.
Oh and 'elated' would definitely be OTT for 2.0.2.  It's just good work, good to have it done.


On 24/08/2012 22:42, Gale Andrews wrote:
| From Vaughan Johnson <> 
| Fri, 24 Aug 2012 14:00:09 -0700
| Subject: [Audacity-quality] Releasing 2.0.2!
On 8/23/2012 8:52 PM, Gale Andrews wrote:
| From Vaughan Johnson <> 
| Thu, 23 Aug 2012 15:31:39 -0700
| Subject: [Audacity-quality] Releasing 2.0.2!
The 48-hour testing cycle on RC4 is completed and there are no P1's or
P2's, so I'm proceeding with Release Process step 6. :-)
I've completed my list, I think, i.e. steps 7 and 8 from:

where "8" is steps 1-9 here: .

Can we please change "delighted" to "pleased" next time? James objected
to "delighted" when I first used it, but I felt it appropriate for 2.0.0
-- but not really for minor releases.  
I thought the objection was to "elated" for 2.0.0: 

so we have downgraded the plus factor for minor releases already. 

But, whatever suits the majority. 

Thanks, everybody!
And to you.


Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
Audacity-quality mailing list