W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

github bug tracking - process proposal

From: Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>
Date: Fri, 27 Sep 2013 15:39:33 +0000
To: Chris Wilson <cwilso@google.com>, Paul Adenot <padenot@mozilla.com>, "Jussi Kalliokoski" <jussi.kalliokoski@gmail.com>, Joe Berkovitz <joe@noteflight.com>
CC: Audio WG <public-audio@w3.org>
Message-ID: <57822D3B-5908-4248-AB38-AD36BE78DEB6@bbc.co.uk>
There was a call for a clearer process on how we are going to use and track issues in github. I propose the following.

1. Use milestones for, well, milestones and specific reviews.
e.g: group all TAG reviews under milestone "TAG Review", things we postpone to a v2 goes into a "V2" milestone, Last Call issues will be tagged "Last Call" and so on.

2. Use tags for specific status / don't close issues unless reviewed

I suggest editors add a "review" tag on issues that have been addressed and (ideally) linked to a change set. We can then easily review them at our teleconference. As a corollary, no issue (unless trivial) should be closed by the editors. That should be something we do during our calls, or done by the chair(s) after review.

3. There is no 3.

Thoughts? Works for everyone?


This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
Received on Friday, 27 September 2013 15:40:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:25 UTC