MDN/Development: Difference between revisions

From MozillaWiki
< MDN
Jump to navigation Jump to search
No edit summary
Line 10: Line 10:
In 2014, the MDN development team adopted Trello for its Continuous Development process. The process revolves around [[/Meetings|2 weekly meetings]] - Planning & Review - where we go thru [https://trello.com/b/p56Gwq46/mdndev-rocks our weekly planning board].
In 2014, the MDN development team adopted Trello for its Continuous Development process. The process revolves around [[/Meetings|2 weekly meetings]] - Planning & Review - where we go thru [https://trello.com/b/p56Gwq46/mdndev-rocks our weekly planning board].


Most items on the board are either bugs that need to be addressed, or enhancements that come from the [[#Roadmap|roadmap].
Most items on the board are either bugs that need to be addressed, or enhancements that come from the [[MDN/Development#Roadmap|roadmap]].


==Roadmap==
==Roadmap==

Revision as of 17:00, 2 September 2014

The MDN site is under active development and is constantly evolving. In addition to the paid engineering, writing and product teams, the MDN community contributes feature requests, helps prioritize work and contributes code to the platform.

The Team

  • Our team
  • You can find us in the #mdndev channel on irc.mozilla.org
  • For regular updates about development status, please join our mailing list.

Development Process

Current

In 2014, the MDN development team adopted Trello for its Continuous Development process. The process revolves around 2 weekly meetings - Planning & Review - where we go thru our weekly planning board.

Most items on the board are either bugs that need to be addressed, or enhancements that come from the roadmap.

Roadmap

The MDN engineering roadmap is significantly influenced by the Developer Relations roadmap, which is a product of a quarterly prioritization process.

Notes from major planning sessions:


Old Processes

(2013) process Overview of the MDN Kanbanery-based development

(2011-2013)Archive of Agile development sprints

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 every 5 minutes:

https://developer-dev.allizom.org/

The dev team pushes commits to stage and production servers when code is ready - often multiple times per day. You can see which commits are on the dev, stage, & production servers here:

http://mzl.la/deployed-mdn

Commits also often include numbers of bugs that you can visit to see relevant discussions.

Platform

For notifications about changes to the MDN, please subscribe to our feed of released changes. For more technical information about a change, click through from that feed entry to the Bugzilla ticket the entry is associated with. You can also follow our feed of all source code commits or watch this page for an overview of commits pushed to production.

All of these resources provide essentially the same information, just in slightly different formats.

Subpages

This is a list of all subpages of this page.