Changes between Initial Version and Version 1 of ReleasePractices/Website


Ignore:
Timestamp:
Jan 24, 2012, 12:16:45 PM (11 years ago)
Author:
Daniel James
Comment:

Starting to write instructions for updating website during release cycle.

Legend:

Unmodified
Added
Removed
Modified
  • ReleasePractices/Website

    v1 v1  
     1This all requires quickbook and python on your path. Working on the live site directly, so check the changes before checking in. The site is checked out from:
     2
     3https://svn.boost.org/svn/boost/website/public_html/live/
     4
     5== Cycle start ==
     6
     7- Copy template from `feed/templates/boost_x_xx_x.qbk` to `feed/history/boost_1_50_0.qbk` (using the appropriate version number).
     8- `svn add` that file.
     9- Edit file to use the correct version number.
     10- Run `site-tools/update.py`.
     11- `svn add` the new release notes file created in `users/history/`.
     12- Check the changes are okay (`dev.rss` should be the only updated feed, also some changes to `generated/state`).
     13
     14== Updating release notes ==
     15
     16- Edit `feed/history/boost_1_50_qbk` (using the appropriate version number).
     17- Run `site-tools/update.py`
     18- Check the changes are okay (if there are no status changes then only the release notes html page, the `dev.rss` feed, and files under `generated/state` should be updated).
     19- Check the changes in.
     20
     21== Add documentation to site (beta and final, requires ssh access, and write permissions for site) ==
     22
     23- ssh into the site
     24- Download the `boost_version.tar.bz2` file using `wget`.
     25- Expand using `tar -xjf`.
     26- Move to site using `sudo mv boost_version /u/grafik/www.boost.org/archives/live/`
     27- Store the compressed file: `sudo mv boost_version.tar.bz2 /u/grafik/www.boost.org/archives/live/zipfiles`
     28
     29== Beta release ==
     30
     31TODO