ReleaseProcess
2051
Comment:
|
2078
|
Deletions are marked like this. | Additions are marked like this. |
Line 23: | Line 23: |
- cd /srv/loco.ubuntu.com | - on cranberry.canonical.com cd /srv/loco.ubuntu.com |
To release the LoCo Directory, you need to follow the following steps:
make sure there are no important merge proposals outstanding
update the translations template (./manage.py update-template), commit the change and push it to trunk
- wait until you get a confirmation mail from LP
download the latest translations
pull the newest trunk (lp:loco-directory)
integrate the newest translations (./manage.py import-translations ~/launchpad-export.tar.gz)
./manage.py compilemessages
- test the release
- commit the translations, push to lp:loco-directory
find out current milestone from https://launchpad.net/loco-directory/+series
./manage.py release <release number>
- commit, push to lp:loco-directory
check out lp:~loco-directory-dev/loco-directory/production
merge trunk release into lp:~loco-directory-dev/loco-directory/production, push
send mail to rt at ubuntu dot com with this or similar content:
Hello everybody, could you please go and update loco.ubuntu.com from lp:~loco-directory-dev/loco-directory/production? Here's the steps that are involved: - on cranberry.canonical.com cd /srv/loco.ubuntu.com - bzr pull lp:~loco-directory-dev/loco-directory/production - cd loco_directory - ./manage.py migrate - ./manage.py compilemessages - (reload apache) Thanks a lot in advance.
- Please make sure additional dependencies, additional steps, etc. need to be document carefully in there.
Hang out in #canonical-sysadmin if the request should take longer.
- Once landed, make sure it all works.
Close all bugs of the active milestone.
- Mark current milestone as released.
Create new milestone in current series.
LoCoTeamPortal/ReleaseProcess (last edited 2013-03-08 21:43:19 by cjohnston)