On 13-01-23 6:55 AM, David Humphrey wrote: > I assume you meant mozilla/webvtt repo when you said "we'll merge into > the mozilla/webrtc repo and work can continue there"? I like this plan.
Yep, thanks for the correction. > My goal with all of the track element bits, plus this parser, is to try > and get things landed and hidden behind a pref so we don't have to > maintain patches against m-c long term, and then fix things in follow-up > bugs. So the roadmap is: - Review the seneca branch filing and fixing issues. - Merge to mozilla/webvtt master when we once we've been through it. - Tag a release version on import that into m-c under bug 833403. - Continue to evolve the webvtt parser in github for a faster cycle time, updating m-c at stable points. In parallel with the above: - Develop mozilla integration code. - Land an integration code in m-c behind a pref. - Iterate from there. One question: right now we're all patching the seneca branch of the parser, but it's not clear where to file bugs. Would people be happier if we worked against a seneca branch of mozilla/webvtt instead of humphd/webvtt? -r _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
