Because of our local timeline we need to commit to 1.1.1 msub to ensure that we can deploy a stable version of Matterhorn that meets our requirements.
Josh, based on our conversation from irc, it sounds like Kristofor should commit his changes to branch commit this to trunk after 1.2 RC1 has been cut and commit separately to our 1.1.1 msub without the changes to the distribution service API. Are we not doing this so that it won't break the other dist impls like stereaming and download?
Without the API changes, how would the contextstrategy access the mp? Is there a way to access it using the mp id?
Should Kristofor commit all of his subsequent changes to both msub and trunk (after 1.2 rc1 has been cut)?
With a 1.1.1 branch, we will not be able to distribute based on any metadata, other than the mediapackage identifier and the media files themselves. Any 1.1.1 branches, will be limited to a single global youtube playlist. This is the work that should go into the 1.1.1 branch.
The rest of the work should be committed to the trunk. These will become two very different code bases.
Is it safe to say that I can commit the Distribution API refactor to trunk now?
No, please wait for the 1.2.x branch to be cut.
I'm deleting this ticket. Each commit should be related to their ticket.