On 7/20/12 12 :04AM, "Nicholas Kwiatkowski" <nicho...@spoon.as> wrote:
>The page has been posted on the staging server. If we could get a few >people to take a peek at it to make sure it looks right, that would be >great. A few confirmations, and I will publish it to production. > >http://flex.staging.apache.org/flex/download.html > >-Nick Nick, Thank you SO much for doing this!! I realized about an hour after I copied the files up that I forgot to rename README to README.txt so that it would show on the website. It's renamed in the staging area (/www/www.apache.org/dist/incubator/flex/4.8.0-incubating/README.txt) but it doesn't look like it got copied. If you can get that page visible I think we should add a link for it under each of the RELEASE_NOTE links in the source and binary sections. I'm sure we will update the RELEASE_NOTES in the coming days so I'd like to know if we need to do anything special when we change one of files (we aren't allowed to change the artifacts for obvious reasons). I'm worried that people are just going to zero in on the binary section and think they can unzip and away they go. I think we need to add a sentence to the binary section that minimally has a link to the Dependencies section (or I'm open to suggestions). If we leave the Dependencies section as is, for the optional components, you need to make it clear that you need every one of those jars, except flex-messaging to enable embedded font support, and you need flex-messaging to enable BlazeDS. We should also add to the release notes that if you try to use BlazeDS and you don't have that jar it blows up in a rather ungraceful fashion (I can do this). Can we put "Please review the release notes before installing or compiling the SDK." in that awful yellow green color you have below or perhaps a nicer color :) Carol
