Labs/Jetpack/FlightDeck/Contribution: Difference between revisions
< Labs | Jetpack | FlightDeck
Jump to navigation
Jump to search
m (→Overview) |
m (→Overview) |
||
Line 11: | Line 11: | ||
If you have questions, ask in [irc://irc.mozilla.org/#jetpack #jetpack on IRC] or on the [http://groups.google.com/group/mozilla-labs-jetpack Jetpack mailing list]. | If you have questions, ask in [irc://irc.mozilla.org/#jetpack #jetpack on IRC] or on the [http://groups.google.com/group/mozilla-labs-jetpack Jetpack mailing list]. | ||
You may also like to read the [[Labs/Jetpack/FlightDeck/Code_Workflow|Code Workflow]] document. | |||
= How to start = | = How to start = |
Revision as of 10:43, 15 July 2010
Overview
- Changes should follow Style Guide
- All changes should be accompanied with test (no front-end tests yet)
- Development should be done on Github
- Every change should have a corresponding bug in bugzilla
- Every change should be developed in a specific branch named bug-12345-human_readable where 123245 is a number of the bug
- There is a number of developers who are able to merge and push from the private branch to the main repository
- Production branch is for production only and it is merged from devel only
If you have questions, ask in #jetpack on IRC or on the Jetpack mailing list. You may also like to read the Code Workflow document.
How to start
- Create github account
- Fork Main repository (it's temporarily on zalun's account)
- Install FlightDeck on your machine - Install instruction
How to commit
- Findor [1] create bug in bugzilla
- create a branch named
git checkout -b bug-12345-name_of_the_feature
- code
- commit changes
- push to your repository
git push origin bug-12345-name_of_the_feature
- provide the link to the commit in bugzilla
Merging
Please always add --no-ff
if using git merge