Re: TTML2 - getting to CR

Using the same filter for ttml2 as this time last week, we now have 21 open issues. 2 are discussed and agreed. 7 are marked for the agenda today.

Additionally there are 7 open "editorial" issues without a pull request, of which 1 is marked for the agenda and also labelled "blocks CR".

In total, 10 open issues are marked "blocks CR", of which 8 have open pull requests.

The 2 "blocks CR" issues without a pull request are both also labelled "agenda":

A single length value for tts:fontSize specifies both height and width.<https://github.com/w3c/ttml2/issues/548>
Incorporate resolutions of additional TTML1 Issues.<https://github.com/w3c/ttml2/issues/358>

Kind regards,

Nigel


From: Nigel Megitt <nigel.megitt@bbc.co.uk<mailto:nigel.megitt@bbc.co.uk>>
Date: Thursday, 25 January 2018 at 18:27
To: 'Timed Text Working Group' <public-tt@w3.org<mailto:public-tt@w3.org>>
Subject: TTML2 - getting to CR
Resent-From: <public-tt@w3.org<mailto:public-tt@w3.org>>
Resent-Date: Thursday, 25 January 2018 at 18:28

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<https://github.com/w3c/ttml2/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+-label%3A%22pr+open%22+-label%3A%22pr+merged%22+-label%3Attml.next+-label%3Aeditorial+> 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