Re: github bug tracking - process proposal

This is fine with me, except I would suggest that milestones are ONLY
milestones - we should use tags for TAG Review, e.g., because it's not a
milestone we need to pass.  Milestones should be V1, last call, V.next.  Or
even drop "last call", and just keep it v1, vnext.


On Fri, Sep 27, 2013 at 8:39 AM, Olivier Thereaux <
Olivier.Thereaux@bbc.co.uk> wrote:

> 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?
>
> --
> Olivier
>
>
>
>
>
> -----------------------------
> http://www.bbc.co.uk
> 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
> immediately.
> Please note that the BBC monitors e-mails
> sent or received.
> Further communication will signify your consent to
> this.
> -----------------------------
>