Thanks to Gale, and everybody for all your hard work on this!
On 4/11/2011 11:23 PM, Gale Andrews wrote:
> Reading from:
> "8 . Post final builds/installers to Google Code and to SourceForge
> (downloads are no longer served from SourceForge, but some users
> still look there, so they should be archived there). Delete the rc's
> from Google Code to avoid user confusion and to conserve space"
> I've done the missing jobs AFAICT.
> * Uploaded the four Windows builds to SF (Linux/Mac were already
> * On GoogleCode, there were a couple of Linux/Mac releases
> not labelled as "Featured" , so I made them so. This label means
> that they appear on our GC Home Page.
> * Also on GoogleCode, I changed the labels for the 1.3.12 releases
> from "Featured" to "Deprecated". The "Deprecated" label means
> that these downloads do not appear on the "Current Downloads"
> "9. Update the zipped manual stored at http://manual.audacityteam.org/help.zip
> using the updated Manual from the source tree. Test unzipping the Manual before
> sending it. When unzipped, it should produce a "help" folder with the "manual"
> folder inside that. "
> Done. Do we want to enable .zip downloads on the Manual to make it easier if
> no-one is around with server access? That means anyone with an account on
> the Manual can upload a zip, but accounts have to be asked for so the account
> holders are us and the translators.
> "10 Release Announcements
> Create the website release announcement and list of changes from the committed
> README.txt. Commit the website changes to SVN and push to the website so that
> it goes into the audacity_website.pot file and is then available to translators.
> Make Forum announcement. Announce release to mailing lists, GoogleCode Wiki,
> SourceForge and the Dreamhost list.
> All done except Dreamhost list which I don't have access to.
> If anyone doesn't like anything about the web changes I made for the release,
> please say. I'm not sure I like bolding the first sentence of the first two
> paragraphs on the front page, though it is more like the "news" underneath.
I think it's better to say, e.g., "Eliminated crashes on Windows..."
instead of "Crashes on Windows", where "crashes" reads as a verb. It
reads as if we implemented some new crashes. Yes, it's in a "Bug Fixes"
section, but later ones are full sentences with verbs, e.g., "Warning
now provided...", "Full support added..." so the "Crashes..." ones are
inconsistent with the rest.
In "other news" (isn't it redundant to say "recent news"? ...especially
as the news item has a date on it), how about mentioning the two recent
Also, I've been meaning to remove the store banner. Please comment it
out from the header. Store is closed.
> Since I've put 1.3.13 above 1.2 in the yellow download box on the front page,
> do we want to put 1.3 above 1.2 in the left navbar on the Download page:
> http://audacity.sourceforge.net/download/ ?
> And swap the download boxes? I'm zero on it - don't think it will make a
> lot of difference but don't object.
Yes, everywhere, 1.3.13 should be more prominent.
Also I did:
Btw, you can do this via TortoiseSVN with the server-side copy by
choosing the "HEAD revision in the repository" radio button in the
Branch/Tag dialog. I'll add that to Release Process.
12. Turn IS_ALPHA back on.
13. Lift the freezes. (Will announce.)