- From: Léonie Watson <tink@tink.uk>
- Date: Tue, 4 Jul 2017 16:27:24 +0100
- To: adanilo@google.com, jsbell@google.com
- Cc: public-html@w3.org
Alex & Josh, The original HTML5.2 timeline [1] is about a month out at present. If we can get issue #829 resolved this week, we should just about be able to get 5.2 to Rec before we run into the Christmas holidays. Much more than a week longer, and we'll be looking at January (and a knock on for HTML5.3 etc.). We really don't want HTML5.2 to move forward without this issue being resolved. IndexedDB has a dependency on it, and it'd be good to move that forward to Rec too, but we need to keep moving on HTML. Questions... 1. Can you get this issue resolved and merged by the end of this week? 2. If not, what is a realistic timetable? If this issue is resolved by the end of this week, our timeline will go something like this (Chaals will correct it if my back/packet calculations are awry): Mon 10th Jul: open CFC for CR. Tue 25th Jul: publish CR (triggers AC review). Mon 9th Oct: open CFC for PR. Tue 24th Oct: publish PR. Wed 22nd Nov: AC review ends. Thu 7th Dec: publish Rec. Léonie. [1] https://lists.w3.org/Archives/Public/public-html/2016Nov/0014.html -- @LeonieWatson @tink@toot.cafe tink.uk Carpe diem
Received on Tuesday, 4 July 2017 15:27:57 UTC