W3C home > Mailing lists > Public > public-tt@w3.org > January 2018

Re: TTML2 - getting to CR

From: Nigel Megitt <nigel.megitt@bbc.co.uk>
Date: Thu, 25 Jan 2018 19:26:38 +0000
To: Pierre-Anthony Lemieux <pal@sandflow.com>, "tmichel@w3.org" <tmichel@w3.org>
CC: Timed Text Working Group <public-tt@w3.org>
Message-ID: <6489CD9E-4801-4049-BD0D-9507726421D2@bbc.co.uk>
I’m actually not certain. Thierry, do you know?

> On 25 Jan 2018, at 18:48, Pierre-Anthony Lemieux <pal@sandflow.com> wrote:
> 
> Hi Nigel,
> 
>> 13 are i18n comments.
> 
> Can you confirm that these will need to be closed (and not merely
> deferred to a future CR) as a matter of process before CR?
> 
> Best,
> 
> -- Pierre
> 
>> On Thu, Jan 25, 2018 at 10:27 AM, Nigel Megitt <nigel.megitt@bbc.co.uk> wrote:
>> All,
>> 
>> We agreed to move to CR of TTML2 by the end of January. I think we have
>> general acceptance that a 2 week slip at this stage would be acceptable,
>> i.e. the proposal to transition would be discussed in the TTWG call on 15th
>> February. However, in order to complete work on the open issues, they all
>> would need a pull request to be opened by 1st February at the latest so that
>> they can be closed within our normal 2 week period, assuming there are no
>> outstanding objections to closing them.
>> 
>> Looking at the ttml2 issues list, and filtering out all those with open or
>> merged pull requests, and all editorial issues, there are 44 open issues.
>> Of those, 6 are discussed and agreed. 13 are i18n comments. So 25 issues
>> have been opened by group members and have no agreed resolution at this
>> stage, and 31 have no open pull request yet.
>> 
>> We are very soon going to have to decide to defer some issues to a future
>> version or slip even further back. Group members have expressed strong views
>> against further slippage in the past and I have no reason to believe the
>> situation has changed. I am treating 15th February as the hard deadline, at
>> which point all required pull requests must have been merged.
>> 
>> This means that the Editors need to know as soon as possible if there are
>> any issues that need particular prioritisation for creating pull requests.
>> 
>> It also means that if any member is intending to raise a formal objection to
>> transitioning to CR based on any particular issues not being resolved, then
>> it would be fair to
>> 
>> a) inform the group of those issues as soon as possible and
>> b) lend a hand preparing pull requests that would resolve them.
>> 
>> I have added a "blocks CR" label to the TTML2 repository. Please could any
>> members who would object to transitioning to CR based on issues not being
>> resolved add this label to the relevant issues. If possible also prepare a
>> pull request in the next week against the issue.
>> 
>> Kind regards,
>> 
>> Nigel
>> 
>> 
>> 


-----------------------------
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.
-----------------------------
Received on Thursday, 25 January 2018 19:29:10 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 January 2018 19:29:10 UTC