RE: Separate milestone for editorial issues ?

Presumably V1Editorial changes would be accepted after June 9th?  Or even June 16th, since they wouldn't reset the CRs?  When might we cut them off?

Jerry

From: Paul Cotton
Sent: Friday, May 13, 2016 9:20 AM
To: Mark Watson <watsonm@netflix.com>; Jerry Smith (IEP) <jdsmith@microsoft.com>; David Dorwin <ddorwin@google.com>; www-archive@w3.org; Matt Wolenetz <wolenetz@google.com>; Philippe Le Hégaret <plh@w3.org>
Subject: RE: Separate milestone for editorial issues ?

>V1Editorial

I agree that it might be useful for the Editors to prioritize the V1Nonblocking issues AFTER all the V1 work is done.  But maybe we should consider adding a separate Editorial tag?


Sent from my Windows 10 phone

From: Mark Watson<mailto:watsonm@netflix.com>
Sent: May 13, 2016 8:06 AM
To: Paul Cotton<mailto:Paul.Cotton@microsoft.com>; Jerry Smith (IEP)<mailto:jdsmith@microsoft.com>; David Dorwin<mailto:ddorwin@google.com>; www-archive@w3.org<mailto:www-archive@w3.org>; Matt Wolenetz<mailto:wolenetz@google.com>; Philippe Le Hégaret<mailto:plh@w3.org>
Subject: Re: Separate milestone for editorial issues ?

I should have addressed this only to editors / chairs.

In addition, it might be useful to have a "Final Review" label. We would replace "needs implementation" with this label when there is a Pull Request available for the issue.

Thoughts ?

...Mark

On Thu, May 12, 2016 at 6:27 PM, Mark Watson <watsonm@netflix.com<mailto:watsonm@netflix.com>> wrote:
We have V1NonBlocking issues, some of which are substantial but only nice-to-have and some of which are purely editorial. I wonder if we should disambiguate them ?

V1Editorial ? I assume we can address such purely editorial issues after June 9th.

...Mark