Difference between revisions of "Releases:Website Checklist"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
# Make sure everything in CVS is correct | # Make sure everything in CVS is correct | ||
# Email yama with a list of changes so jp.cb.o can be updated in time | # Email yama with a list of changes so jp.cb.o can be updated in time | ||
| + | |||
| + | |||
| + | == Camino 1.0.1 == | ||
| + | This is the process as we did it for Camino 1.0.1: | ||
Revision as of 22:19, 18 April 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
- File bug with final release notes in it (get review and checkin)
- Email Ludo with final release notes
- Create release notes on website
- 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
Camino 1.0.1
This is the process as we did it for Camino 1.0.1:
