MozillaWiki:Team: Difference between revisions

Jump to navigation Jump to search
added a section explaining the release process for MozillaWiki
(added a section explaining the release process for MozillaWiki)
Line 85: Line 85:
** Mozilla-wide wiki gardening campaigns and hackathons
** Mozilla-wide wiki gardening campaigns and hackathons


== Release Processes ==
We release changes to MozillaWiki weekly on Thursdays. We track release planning on [[MozillaWiki:Releases]] subpages. Once the release is complete, post an announcement explaining the changes to [[MozillaWiki:News]].
All feature and change requests are tracked in Bugzilla, under Websites > wiki.mozilla.org.
The process for a feature or change request to be implemented in production is as follows:
# [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=wiki.mozilla.org File a bug].
# Members of MozillaTeam will triage the bug accordingly, modifying whiteboard, milestone and other fields accordingly.
# The request will be evaluated for suitability on MozillaWiki during a MozillaWiki community call ([[#How_to_Participate|held twice monthly]). Decisions during community calls are generally made by [http://nowviskie.org/2012/lazy-consensus/ lazy consensus], with MozillaWiki module owners and/or peers making the final call if necessary.
# If MozillaWiki team determines the change should be implemented, it will be rolled out to our development instance first. While it implemented on dev, it will undergo testing and security review (if required).
# Once the change has been tested and passed security review (if required), it will be pushed out to stage and finally production.
=== Requesting features and changes ===
To request a change or feature, please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=wiki.mozilla.org file a bug.]
== How to Participate ==
== How to Participate ==


canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,698

edits

Navigation menu