Re: Choosing a CR end date

Hi Simon,

I think the W3C process requires 4 weeks between the date we transition to
Proposed Recommendation and the date we finally publish the final Rec.
Those 4 weeks are provided for all the W3C Advisory Committee reps to
review the spec and WBS survey
https://www.w3.org/2002/09/wbs/33280/webdriver-cr/ and to indicate whether
they support making the spec a Rec or whether they have objections.

That suggests we’d need to set the CR end date at mid-August in order to
provide time to do the transition to PR plus the 4 weeks for AC review.

  —Mike

Simon Stewart <simon.m.stewart@gmail.com>, 2017-03-29 16:47 +0100:
> Archived-At: <http://www.w3.org/mid/CAOrAhYEm9SocQ1LeNR8UR7kiFXHQnB2RRtAN+Qyyu-OYbUN9bA@mail.gmail.com>
> 
> Hi everyone,
> 
> Following up on the public list after several private discussions. I'm
> still waiting for suggestions for a proposed end date from (in alphabetical
> order) Apple, Google, Microsoft, Mozilla, and (technically) the Selenium
> project.
> 
> I'm going to suggest September 30th, 2017. That hopefully gives us enough
> time to get the test suite into shape. Does anyone want to suggest an
> alternative date?
> 
> Simon
> 
> On Tue, Feb 21, 2017 at 10:45 AM, Simon Stewart <simon.m.stewart@gmail.com>
> wrote:
> 
> > Hi everyone,
> >
> > There are a couple of fixes that need to go in (around broken links), but
> > we're now ready to move to CR. According to Mike[tm] Smith, the most
> > significant thing we need to do right now is to choose a CR end date.
> >
> > So, what date do we pick? The 31st March feels a little close given that
> > the only spec-compliant end-node I'm aware of is geckodriver (and that's
> > still has the new session stuff and the pointer actions to land) Would
> > someone from MS, Google, and/or Apple be able to offer some input on a
> > realistic date we should be targeting?
> >
> > Many thanks,
> >
> > Simon
> >

-- 
Michael[tm] Smith https://people.w3.org/mike