Difference between revisions of "Releases:Website Checklist"
Jump to navigation
Jump to search
(anchors) |
|||
Line 6: | Line 6: | ||
# File bug with final release notes and ReadMe.rtf (if applicable) in it (get review and checkin) | # File bug with final release notes and ReadMe.rtf (if applicable) in it (get review and checkin) | ||
# Email Ludo with final release notes and ReadMe.rtf | # Email Ludo with final release notes and ReadMe.rtf | ||
− | # Create release notes on website | + | # Create release notes on website (including anchors for each of the sections, i.e., for easy linking to Known Issues) |
# Update htaccess file so that /releases/latest points to the new relnotes | # Update htaccess file so that /releases/latest points to the new relnotes | ||
# Get release version into Bouncer (pending final release file) | # Get release version into Bouncer (pending final release file) |
Revision as of 23:13, 23 June 2006
When preparing for a release, the following things need to be done (this list will probably need to be arranged in an "order" as appropriate):
- Create release notes on wiki
- Create release notes RTF
- Review ReadMe.rtf and change as needed (file is fairly static; mostly version # changes)
- File bug with final release notes and ReadMe.rtf (if applicable) in it (get review and checkin)
- Email Ludo with final release notes and ReadMe.rtf
- Create release notes on website (including anchors for each of the sections, i.e., for easy linking to Known Issues)
- Update htaccess file so that /releases/latest points to the new relnotes
- Get release version into Bouncer (pending final release file)
- Create download links (/download/releases/VERSION# and /download/releases/VERSION#-MultiLang)
- Create new "news" notification (remember atom file)
- Update main page version number(s)
- Update agentdetect scripts
- Make sure everything in CVS is correct
- Email yama with a list of changes so jp.cb.o can be updated in time
- Update www.m.o htaccess files to point to cb.o relnotes
- Update www.m.o/project/camino/homepage.html to list new release
Camino 1.0.1
This is the process as we did it for Camino 1.0.1: