This repository has been archived by the owner on May 10, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 264
How to Branch The Trains
Jared Hirsch edited this page Apr 20, 2014
·
16 revisions
Persona development occurs in cycles, or "trains". A dynamic schedule is available.
Trains "roll" every other Wednesday afternoon, a process which involves creating a branch, documenting its changes and notifying interested parties. Here's the checklist:
- create three branches from the appropriate commit (usually tip of dev)
- a public branch named
train-YYYY.MM.DD
- a private branch named
train-YYYY.MM.DD-secfixes
- a private branch named
train-YYYY.MM.DD-release
- go through the diffs since the previous train and update the ChangeLog (example)
- commit the changelog to
train-YYYY.MM.DD
anddev
in the public repo - bump the version in
dev
inscripts/browserid.spec
and the changelog (example) - open a bugzilla bug to deploy the train to stage (assign to @jrgm) (example)
- ping mathjazz and let him know the train is cut and l10n can proceed. also copy the dev-identity list (example)
- update the translation preview environment by cherry-picking the magic commit (533cbe8) and following the instructions appended thereto
Once the train is ready to go, it can be released.