You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 10, 2019. It is now read-only.
Trains "roll" every other friday afternoon, a process which involves creating a branch, documenting its changes and notifying interested parties. Here's the checklist:
create a branch from the appropriate commit (usually tip of dev)
by convention, the branch is named train-YYYY.MM.DD
go through the diffs since the previous train and update the ChangeLog (example)
commit the changelog to the train
merge the changelog to dev
bump the version in dev in scripts/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)