MDN/Archives/Development/Redesign/Testing: Difference between revisions

MDN/Archives/Development/Redesign/Testing (view source)

238 bytes added , 6 November 2013

Confirmed users

556

edits

@@ Line 46: / Line 46: @@
 *Bugs that can be [https://bugzilla.mozilla.org/showdependencytree.cgi?id=925145&hide_resolved=1 addressed after launch]
-We can follow what is being released by tracking the development on GitHub:
+=== Following development in real time ===
-https://github.com/mozilla/kuma/commits/master
+If you want to stay in the loop on a bug or a set of bugs, be sure to '''add yourself to the "cc" list'''. Designers and developers update bugs with discussions and decisions as they go. A github robot will automatically comment on bugs when corresponding code is merged into the master line of development. Those commits are automatically pushed to the dev server:
-Commits often include bug numbers that we can look up to see relevant discussions. Commits in master are automatically pushed to the dev server:
 https://developer-dev.allizom.org/
-Commits are then pushed to stage and prod servers by the dev team, usually daily but sometimes it takes a couple days:
+The dev team pushes commits to stage and production servers when the code is ready. You can see which commits are on the stage & production servers here:
-https://developer.allizom.org/
+http://mzl.la/mdn_whats_deployed
-https://developer.mozilla.org/
+Commits also often include numbers of bugs that you can visit to see relevant discussions.
 ===Weekly Meeting Notes===