Confirmed users
508
edits
Mozilla.com/Workflow-improvements: Difference between revisions
Mozilla.com/Workflow-improvements (view source)
Revision as of 07:46, 14 January 2011
, 14 January 2011no edit summary
No edit summary |
No edit summary |
||
| Line 93: | Line 93: | ||
* Since it's all done for you, git keeps a very good history of what went on. This lets us generate cool graphs and statistics about the codebase to see what's going on and helps us to improve our process more and more. | * Since it's all done for you, git keeps a very good history of what went on. This lets us generate cool graphs and statistics about the codebase to see what's going on and helps us to improve our process more and more. | ||
=== Releases & one-offs === | |||
A big problem with mozilla.com is that there is a high number of small changes which always need to go out ASAP, as well as larger changes that trickle in over time. We want to start doing rolling releases ever 2 weeks, with the occasional one-off. | |||
The above process describes what would happen with a one-off, so a one-off changes are easily supported. For a release cycle, the developer would merge his/her bugfix branch into master but not push it out. When time comes to publish a release, all it takes is publishing the master branch (an easy git command). | |||
=== Other notes === | === Other notes === | ||