When the PMC approves a new SDK (or other product) version, touch the following places :
- Add an entry to the Apache Blog announcing the new version.
- Update download-binaries.cmsPage with new version number. Update links to new binaries download.
- Update download-source.cmsPage with new version number. Update links to new source download.
- Update doap_Flex.rdf with new version number and related info.
- Update SDK installer. This usually involves updating the sdk-installer-config-2.0.xml file, but it could be more involved if the SDK Installer is being updated at the same time.
- Update the ../templates/flex-v2-footer.html file with the new version number.
- Update index.cmsPage and add the new news item (blog post) to the page.
- Update the /asdocs/, if needed. The SVN only allows ~500 pages per commit or it starts to give weird errors. Keep this in mind and commit thoughtfully.
- Watch the homepage slideshow. If a previous version number was included in one of the slides, it may need to be updated. Check the /flex/site/trunk/content/images/slider*.png files. Comps (PSD) files are located in the comps folder for easy editing and re-exporting.
- Update version number used in examples in http://flex.apache.org/doc-getstarted.html
- JIRA (set to 'released' and create next version number as 'unreleased')
Try to do as much (except for /asdocs/) in one commit, if possible. Touching anything in the templates directory will cause a rebuild, which will cause buildbot to process files for up to 15 minutes, and not take additional changes.