Re: Generating June 9 working drafts

I merged the PR (Thanks Philippe). FYI, I made a few small cleanup commits
directly in the last hour.

I'm looking at #225 now.

On Thu, Jun 9, 2016 at 6:27 PM, Mark Watson <watsonm@netflix.com> wrote:

> I've reviewed all David's changes for EME and it all looks good to me.
>
> I also think we should merge #225, but am waiting for word from David
> since he explicitly commented that he intended to review.
>
> ...Mark
>
> On Thu, Jun 9, 2016 at 6:24 PM, Jerry Smith (WPT) <jdsmith@microsoft.com>
> wrote:
>
>> You are quick, Philippe.  I wondered how the PR merged change made it to
>> your CR copy.
>>
>> MSE looks ready to me.
>>
>> David's made a number of changes for EME #117.  When he is done with
>> final changes, it should be good.  I believe it is acceptable for CR now.
>>
>> It looks like Mark's pull request to fix #225 (
>> https://github.com/w3c/encrypted-media/pull/232)  is ready.  It's a
>> pretty direct change and fixes two errors caught by David.  I suggest it be
>> merged as well.
>>
>> There are currently no open V1 issues on MSE, and only #110 and #85 on
>> EME.  David has indicated that #110 won't close tonight.
>>
>> Jerry
>>
>>
>> -----Original Message-----
>> From: Philippe Le Hegaret [mailto:plh@w3.org]
>> Sent: Thursday, June 9, 2016 6:14 PM
>> To: Matt Wolenetz <wolenetz@google.com>; Paul Cotton <
>> Paul.Cotton@microsoft.com>
>> Cc: David Dorwin <ddorwin@google.com>; Mark Watson <watsonm@netflix.com>;
>> Jerry Smith (WPT) <jdsmith@microsoft.com>; public-hme-editors@w3.org
>> Subject: Re: Generating June 9 working drafts
>>
>> And I updated the branch.
>>
>> https://rawgit.com/w3c/media-source/v1-CR-ready/index.html
>>
>> #91 is closed.
>>
>> Philippe
>>
>>
>> On 06/09/2016 09:12 PM, Matt Wolenetz wrote:
>> > MSE: last at risk item was just now merged in.
>> >
>> > On Thu, Jun 9, 2016 at 6:06 PM, Paul Cotton <Paul.Cotton@microsoft.com
>> > <mailto:Paul.Cotton@microsoft.com>> wrote:
>> >
>> >     I am back at my desk.____
>> >
>> >     __ __
>> >
>> >     MSE:  I believe we are ready to go once we have the last at risk
>> >     item merged in. ____
>> >
>> >     __ __
>> >
>> >     EME:  Where do we stand?____
>> >
>> >     __ __
>> >
>> >     /paulc____
>> >
>> >     __ __
>> >
>> >     *From:*Paul Cotton [mailto:Paul.Cotton@microsoft.com
>> >     <mailto:Paul.Cotton@microsoft.com>]
>> >     *Sent:* Thursday, June 9, 2016 5:07 PM
>> >
>> >
>> >     *To:* David Dorwin <mailto:ddorwin@google.com <mailto:
>> ddorwin@google.com>>;
>> >     Mark Watson <mailto:watsonm@netflix.com <mailto:watsonm@netflix.com
>> >>;
>> >     Matthew Wolenetz <mailto:wolenetz@google.com <mailto:
>> wolenetz@google.com>>
>> >     (mailto:wolenetz@google.com <mailto:wolenetz@google.com>)
>> >     <mailto:wolenetz@google.com <mailto:wolenetz@google.com>>; Jerry
>> Smith
>> >     (WPT) <mailto:jdsmith@microsoft.com <mailto:jdsmith@microsoft.com
>> >>;
>> >     Philippe Le Hegaret (mailto:plh@w3.org <mailto:plh@w3.org>) <
>> plh@w3.org
>> >     <mailto:plh@w3.org>>
>> >     *Cc:* mailto:public-hme-editors@w3.org <mailto:
>> public-hme-editors@w3.org>
>> >     *Subject:* RE: Generating June 9 working drafts____
>> >
>> >     __ __
>> >
>> >     I will NOT send out any CfC until I have FIRM confirmation from the
>> >     Editors that the drafts are READY.____
>> >
>> >     __ __
>> >
>> >     /paulc____
>> >
>> >     __ __
>> >
>> >     *From:*Paul Cotton [mailto:Paul.Cotton@microsoft.com]
>> >     *Sent:* Thursday, June 9, 2016 5:02 PM
>> >     *To:* David Dorwin <mailto:ddorwin@google.com <mailto:
>> ddorwin@google.com>>;
>> >     Mark Watson <mailto:watsonm@netflix.com <mailto:watsonm@netflix.com
>> >>;
>> >     Matthew Wolenetz <mailto:wolenetz@google.com <mailto:
>> wolenetz@google.com>>
>> >     (mailto:wolenetz@google.com <mailto:wolenetz@google.com>)
>> >     <mailto:wolenetz@google.com <mailto:wolenetz@google.com>>; Jerry
>> Smith
>> >     (WPT) <mailto:jdsmith@microsoft.com <mailto:jdsmith@microsoft.com
>> >>;
>> >     Philippe Le Hegaret (mailto:plh@w3.org <mailto:plh@w3.org>) <
>> plh@w3.org
>> >     <mailto:plh@w3.org>>
>> >     *Cc:* mailto:public-hme-editors@w3.org <mailto:
>> public-hme-editors@w3.org>
>> >     *Subject:* RE: Generating June 9 working drafts____
>> >
>> >     __ __
>> >
>> >     FYI, I am going out to a business appointment at 5:45pm EDT this
>> >     evening and will be away from my desk until approximately 9pm EDT.
>> >        I would appreciate someone in the PDT zone replying to this
>> >     message before 9pm EDT (6pm PDT) giving me the current status of
>> >     each of the specs.____
>> >
>> >     __ __
>> >
>> >     /paulc____
>> >
>> >     __ __
>> >
>> >     *From:*David Dorwin [mailto:ddorwin@google.com]
>> >     *Sent:* Thursday, June 9, 2016 3:19 PM
>> >     *To:* Mark Watson <mailto:watsonm@netflix.com <mailto:
>> watsonm@netflix.com>>
>> >     *Cc:* Paul Cotton <Paul.Cotton@microsoft.com
>> >     <mailto:Paul.Cotton@microsoft.com>>; Jerry Smith (WPT)
>> >     <mailto:jdsmith@microsoft.com <mailto:jdsmith@microsoft.com>>;
>> >     mailto:public-hme-editors@w3.org <mailto:public-hme-editors@w3.org>
>> >     *Subject:* Re: Generating June 9 working drafts____
>> >
>> >     __ __
>> >
>> >     I am focused on this all day as I have been all week. I agree, I
>> >     think we will be able to get the major blocking issues addressed. I
>> >     think review turnaround will be the bottleneck going forward.____
>> >
>> >     __ __
>> >
>> >     I have two outstanding pull requests. The first is fairly large and
>> >     touches a lot of text, so we should try to land that ASAP to avoid
>> >     conflicts.____
>> >
>> >       * https://github.com/w3c/encrypted-media/pull/238____
>> >       * https://github.com/w3c/encrypted-media/pull/235____
>> >
>> >     __ __
>> >
>> >     Those two PRs address most of #117 and #231, respectively. There is
>> >     some refactoring to be done to wrap up #117, but that depends on
>> >     landing #238. The refactoring should be straightforward.____
>> >
>> >     __ __
>> >
>> >     #110 is mostly fixed, but there is some discussion there. I doubt we
>> >     will reach a conclusion on that today. #233 is essentially an IDL
>> >     discussion. We could make a change, but I'm not sure we'll have
>> >     confirmation on the correctness today.____
>> >
>> >     __ __
>> >
>> >     Note: I believe the registry links will be broken unless we land
>> >     https://github.com/w3c/encrypted-media/pull/213. I provided
>> >     feedback. Philippe, what is your plan here?____
>> >
>> >     __ __
>> >
>> >     On Thu, Jun 9, 2016 at 11:54 AM, Mark Watson <watsonm@netflix.com
>> >     <mailto:watsonm@netflix.com>> wrote:____
>> >
>> >         I am available most of today to work on the remaining issues. I
>> >         expect we can get them done. But since no time zone was attached
>> >         to the June 9 deadline, it might be best for Phillipe to expect
>> >         to produce the working drafts tomorrow.____
>> >
>> >         __ __
>> >
>> >         ...Mark____
>> >
>> >         __ __
>> >
>> >         On Thu, Jun 9, 2016 at 11:50 AM, Paul Cotton
>> >         <mailto:Paul.Cotton@microsoft.com <mailto:
>> Paul.Cotton@microsoft.com>>
>> >         wrote:____
>> >
>> >             Can you please give us an update on when the remaining EME
>> >             V1 issues will be closed?  Can you get them ALL done today
>> >             as planned?
>> >
>> >             /paulc____
>> >
>> >
>> >             -----Original Message-----
>> >             From: Philippe Le Hegaret [mailto:plh@w3.org
>> >             <mailto:plh@w3.org>]
>> >             Sent: Thursday, June 9, 2016 2:40 PM
>> >             To: Jerry Smith (WPT) <jdsmith@microsoft.com
>> >             <mailto:jdsmith@microsoft.com>>; Matt Wolenetz
>> >             <mailto:wolenetz@google.com <mailto:wolenetz@google.com>>;
>> Paul
>> >             Cotton <Paul.Cotton@microsoft.com
>> >             <mailto:Paul.Cotton@microsoft.com>>
>> >             Cc: David Dorwin <ddorwin@google.com
>> >             <mailto:ddorwin@google.com>>; Mark Watson
>> >             <mailto:watsonm@netflix.com <mailto:watsonm@netflix.com>>;
>> >             mailto:public-hme-editors@w3.org <mailto:
>> public-hme-editors@w3.org>
>> >             Subject: Re: Generating June 9 working drafts
>> >
>> >             I'm testing around #91.
>> >
>> >             http://jay.w3.org/~plehegar/trackdefault.html
>> >             <http://jay.w3.org/%7Eplehegar/trackdefault.html>
>> >             http://jay.w3.org/~plehegar/trackdefaultlist.html
>> >             <http://jay.w3.org/%7Eplehegar/trackdefaultlist.html>
>> >
>> >             As far as I can tell, only Chrome implements this part. I
>> >             tried on Edge and Firefox and it doesn't seem to work at
>> all.
>> >
>> >             Is that correct?
>> >
>> >             Philippe
>> >
>> >             On 06/09/2016 02:13 PM, Jerry Smith (WPT) wrote:
>> >              > Just commented on #91.  The kinds sequence needs to be
>> >             accessed from
>> >              > within an algorithm.  Is that simple to do?  If so, this
>> >             doesn’t look hard.
>> >              >
>> >              > Jerry
>> >              >
>> >              > *From:*Matt Wolenetz [mailto:wolenetz@google.com
>> >             <mailto:wolenetz@google.com>]
>> >              > *Sent:* Thursday, June 9, 2016 11:12 AM
>> >              > *To:* Paul Cotton <Paul.Cotton@microsoft.com
>> >             <mailto:Paul.Cotton@microsoft.com>>
>> >              > *Cc:* David Dorwin <ddorwin@google.com
>> >             <mailto:ddorwin@google.com>>; Jerry Smith (WPT)
>> >              > <mailto:jdsmith@microsoft.com <mailto:
>> jdsmith@microsoft.com>>;
>> >             Philippe Le Hegaret (mailto:plh@w3.org <mailto:plh@w3.org>)
>> >              > <mailto:plh@w3.org <mailto:plh@w3.org>>; Mark Watson
>> >             <mailto:watsonm@netflix.com <mailto:watsonm@netflix.com>>;
>> >              > mailto:public-hme-editors@w3.org <mailto:
>> public-hme-editors@w3.org>
>> >              > *Subject:* Re: Generating June 9 working drafts
>> >              >
>> >              > #5 is fixed, so MSE v1 only has #91 remaining.
>> >              >
>> >              > On Thu, Jun 9, 2016 at 8:25 AM, Matt Wolenetz
>> >             <mailto:wolenetz@google.com <mailto:wolenetz@google.com>
>> >              > <mailto:wolenetz@google.com
>> >             <mailto:wolenetz@google.com>>> wrote:
>> >              >
>> >              >     Both of the MSE issues are pending action from other
>> >             editors:
>> >              >
>> >              >     #5 has a PR pending review.
>> >              >     #91 needs input. Philippe, can you help on that one,
>> >             since it's
>> >              >     related to a problem with webidl and the recent
>> >             sequence type change
>> >              >     in MSE?
>> >              >
>> >              >     Matt
>> >              >
>> >              >     On Jun 9, 2016 8:10 AM, "Paul Cotton"
>> >             <mailto:Paul.Cotton@microsoft.com <mailto:
>> Paul.Cotton@microsoft.com>
>> >              >     <mailto:Paul.Cotton@microsoft.com
>> >             <mailto:Paul.Cotton@microsoft.com>>> wrote:
>> >              >
>> >              >         EME V1 issues (6 including ISSUE-85):
>> >              >
>> >              >
>> https://github.com/w3c/encrypted-media/issues?milestone=1
>> >              >
>> >              >         MSE V1 issues (2):
>> >              >
>> >              > https://github.com/w3c/media-source/issues?milestone=2
>> >              >
>> >              >         Philippe is ready to generate the June 9 MSE and
>> >             EME working
>> >              >         drafts that will be referenced in the WG CfC’s to
>> >             publish them
>> >              >         as Candidate Recommendations.
>> >              >
>> >              >         When will the Editors be done with V1 issues?
>> >              >
>> >              >         /paulc
>> >              >
>> >              >         Paul Cotton, Microsoft Canada
>> >              >
>> >              >         17 Eleanor Drive, Ottawa, Ontario K2E 6A3
>> >              >
>> >              >         Tel: (425) 705-9596 <tel:%28425%29%20705-9596>
>> >             <tel:%28425%29%20705-9596> Fax: (425)
>> >              >         936-7329 <tel:%28425%29%20936-7329>
>> >              >____
>> >
>> >         __ __
>> >
>> >     __ __
>> >
>> >
>>
>
>

Received on Friday, 10 June 2016 01:29:54 UTC