Platform/Layout: Difference between revisions

Platform/Layout (view source)

Revision as of 16:18, 15 July 2019

91 bytes removed , 15 July 2019

Updating bug triage guidelines, listing meetings

Svoisen

154

edits

@@ Line 13: / Line 13: @@
 * '''IRC''': [https://irccloud.mozilla.com/#!/ircs://irc1.dmz.scl3.mozilla.com:6697/%23layout #layout on irc.mozilla.org]
+* '''Slack''': #layout on Slack (MoCo employees only)
 * '''E-mail''': [https://lists.mozilla.org/listinfo/dev-tech-layout dev-tech-layout@lists.mozilla.org]
+== Team Meetings ==
+=== Weekly Standups ===
+=== Post-release Retrospectives ===
+=== CSS Working Group Strategy Meetings ===
+=== Bug Triage Meetings ===
 == Roadmap and Status ==
@@ Line 23: / Line 34: @@
 == Release Notes ==
-View [https://wiki.mozilla.org/Platform/Layout/ReleaseNotes notes and lists of all fixed layout bugs] for a given release.
+We publish [https://wiki.mozilla.org/Platform/Layout/ReleaseNotes notes and lists of all fixed layout bugs] for a given release. These release notes call out items of particular importance (new features, webcompat fixes) that may be helpful for web content authors.
 == Filing a Bug ==
@@ Line 51: / Line 62: @@
 * [https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=SVG SVG]
-== Bug Triage Guidelines ==
+== Bug Triage and Whiteboard Tagging Guidelines ==
-We use [https://bugzilla.mozilla.org Bugzilla] to track a combination of both bugs and new features. As such, we employ a hybrid system of Bugzilla priority and, optionally, a backlog priority (noted as <code>[layout:pX]</code> in the bug's whiteboard field). This allows us the flexibility of indicating high-priority backlog items that may still be lower in priority than crashes or security bugs, which should be addressed immediately. Typically, only items with P2 or P3 priority will also have a layout backlog priority in the whiteboard field.
+We use [https://bugzilla.mozilla.org Bugzilla] to track a combination of both bugs and new features. As such, we employ a hybrid system of Bugzilla priority and, optionally, a backlog tag (noted as <code>[layout:backlog:YYYYqQ]</code> in the bug's whiteboard field). The backlog tag, if provided, indicates the intended quarter and/or target release in which we intend to work on and ship a given feature. For instance, a tag of `[layout:backlog:2019q3]` indicates that we will attempt to work on the bug in Q3 of 2019.
 === Getting Started ===
@@ Line 62: / Line 73: @@
 * '''Priority 1 (P1)''': Blocker, crash or very high-impact performance or web compatibility bug. Must-fix in the current iteration. The severity of the P1 should generally be set accordingly.
-* '''Priority 2 (P2)''': High-priority bug that should be in-progress or will be worked on next. Includes moderately high-impact performance or web compatibility bugs.
+* '''Priority 2 (P2)''': High-priority bug that should be in-progress and fixed within the next two releases. Includes moderately high-impact performance or web compatibility bugs.
 * '''Priority 3 (P3)''': Normal-priority bug or a backlog item.
 * '''Priority 4 (P4)''': Low-priority bug or managed by a bot (such as an intermittent test failure). We are unlikely to devote resources to these bugs any time soon.
-* '''Priority 5 (P5)''': Icebox. We do not plan to spend time on these bugs but we will accept patches.
+* '''Priority 5 (P5)''': We do not plan to spend time on these bugs but we will accept patches.
-=== Layout Backlog Priority ===
-* '''Priority 1 [layout:p1]''': Highest-priority backlog item. Typically a must-have. We are working on this or plan to work on it soon for the next release.
-* '''Priority 2 [layout:p2]''': Normal-priority backlog item. We will address after P1-level items we have targeted for the near-term. Likely to land in the next release or release following.
-* '''Priority 3 [layout:p3]''': Low-priority backlog item.
 == Contributing ==