Le 03/04/2013 23:00, Alex Keybl a écrit : >> But from Gaia's point of view I absolutely support going back to using >> master for 1.1. I'd like to see us branch gaia releases as late as possible >> (if at all), and only allow bugfixes on that branch (not new features or >> enhancements). > I think this is a good point - separating out taking tip of Gecko/Gaia for an > upcoming Firefox OS release. That being said, I'm not certain we can pause > from v1.1 development long enough to seriously evaluate the quality of master > and determine whether it's a viable switch in the next month. > > Perhaps we should change the topic to being "Going back to m-c and/or gaia > master for v1.2" >
Agreed, this is too late for v1.1. But as long as we have a clear path to doing that in a future version I'm happy. To minimize the number of gecko branches, I think we ultimately need to use ESR versions of gecko in B2G, because we'll need a long-standing branch for the gecko used in B2G anyway. I don't know which version is planned to be the next ESR but it's worth having this version as our goal for v1.2 (or v2). Another (maybe braindead) thought: as I understand, it's difficult for us to use the gecko stable branch using the normal train because we'd need to land too many patches. Then, maybe we can use the beta branch as B2G stable branch. I told you it was gonna be dumb. -- Julien
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
