Confirmed users
556
edits
MDN/Archives/Development/Redesign/Testing: Difference between revisions
MDN/Archives/Development/Redesign/Testing (view source)
Revision as of 13:42, 6 November 2013
, 6 November 2013→Following development in real time
Groovecoder (talk | contribs) |
Groovecoder (talk | contribs) |
||
| Line 48: | Line 48: | ||
=== Following development in real time === | === Following development in real time === | ||
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: | 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 every 5 minutes: | ||
https://developer-dev.allizom.org/ | https://developer-dev.allizom.org/ | ||
| Line 56: | Line 56: | ||
http://mzl.la/mdn_whats_deployed | http://mzl.la/mdn_whats_deployed | ||
Commits also often include numbers of bugs that you can visit to see relevant discussions. | Commits also often include numbers of bugs that you can visit to see relevant discussions. | ||
===Weekly Meeting Notes=== | ===Weekly Meeting Notes=== | ||