- From: Chris Lilley <chris@w3.org>
- Date: Mon, 11 Jun 2018 17:36:40 -0400
- To: Bogdan Brinza <bbrinza@microsoft.com>, "www-svg@w3.org" <www-svg@w3.org>
- Cc: "Liam R. E. Quin" <liam@w3.org>
Received on Monday, 11 June 2018 21:46:45 UTC
Hi Bogdan On 11-Jun-18 16:48, Bogdan Brinza wrote: > Milestone changes: > > * Deleted milestones: SVG3, SVG Core Cleanup > * Created/updated milestones: SVG 2.0 Updated Candidate > Recommendation, SVG 2.0 Recommendation, SVG 2.1 Working Draft > > Chris / Liam – I didn’t identify any changes that should block SVG 2.0 > Updated CR publication, how should we proceed from here? > As we discussed on the call, issues for 2.0 which are fully resolved should preferably have the edits done before publication of the next CR. That way, commentors can see in-place how the edits respond to their issues. Having a transition request ready for the next CR should be doable by the start of July. Issues which are for 2.0 but not fully resolved, will need to wait for a later CR. There cannot be substantive changes after CR; thus, all the items assigned to the 2.0 Rec milestone need to be resolved and the edits in place before the final CR is published. -- Chris Lilley @svgeesus Technical Director @ W3C W3C Strategy Team, Core Web Design W3C Architecture & Technology Team, Core Web & Media
Received on Monday, 11 June 2018 21:46:45 UTC