RE: Draft MSE Proposed Recommendation and VNext branch

This makes sense to me:


-          Proceed with preparing a PR for MSE

-          Postpone any work to create a VNext branch until PR work is completed

Paul:  Is there an advantage to having a FPWD soon for VNext that I’m missing?

Jerry

From: Matt Wolenetz [mailto:wolenetz@google.com]
Sent: Thursday, August 25, 2016 4:36 PM
To: Paul Cotton <Paul.Cotton@microsoft.com>
Cc: Mark Watson <watsonm@netflix.com>; Jerry Smith (WPT) <jdsmith@microsoft.com>; Philippe Le Hegaret (plh@w3.org) <plh@w3.org>; public-hme-editors@w3.org
Subject: Re: Draft MSE Proposed Recommendation and VNext branch

My vote is yes, please prepare the draft MSE PR.
For VNext, I'm not focused on those at the moment. I don't want to deprioritize/distract getting to PR and REC.

Please, can we resolve what to do about branching and VNext/FPWD after the push to getting PR CfC out the door?

On Tue, Aug 23, 2016 at 1:57 PM, Paul Cotton <Paul.Cotton@microsoft.com<mailto:Paul.Cotton@microsoft.com>> wrote:
Given that there are no outstanding MSE V1 issues [1] (except related to the MSE registry [2]), are we ready for Philippe to prepare a draft MSE Proposed Recommendation so that it can be ready for a HME WG CfC?

Do the Editors also want Philippe to create a MSE VNext branch [3] so they can a) add back in the removed at risk features and/or b) continue working on VNext issues?

If possible I believe we should publish a MSE VNext FPWD at about the same time as we publish the Proposed Recommendation.

/paulc

[1] https://github.com/w3c/media-source/issues

[2] https://github.com/w3c/media-source/issues/74

[3] https://lists.w3.org/Archives/Public/public-html-media/2016May/0039.html


Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596<tel:%28425%29%20705-9596> Fax: (425) 936-7329<tel:%28425%29%20936-7329>