On Jul 30, 2013, at 8:13 AM, Julien Wajsberg <[email protected]> wrote:
> Le 23/07/2013 08:58, Tim Chien a écrit : >> Hi all, >> >> Do we need to support Gaia master + b2g18? If memory serves me right, >> I remember we don't have to support this kind of combination, but I >> would like to get a hard confirmation on this. Thanks. >> > > I already asked this question several times, and the same answer has > been given since then: no we don't need to support this. > > Still, some people (including me) are still using this combination > because it makes it easier to develop on Gaia, and there has been > (limited) efforts to make this combination work. Isnt it better to fix the problems now, and get more developers onto master/m-c as soon as possible? if you guys encounter issues that is blocking development, this should raise the urgency to fix it. i feel that working in a unsupported development like master/b2g18 is only going to create fragmentation and not give attention to fixing the environment we want. FWIW, our QA team is actively testing against master/m-c, and filing bugs furiously to get this branch stable. I really suggest devs work in the environment also so we can iron out those kinks soon than later. Also, releng, a-team, and other supporting cast are all focused on working in master/m-c; not master/b2g18. Tony > > When we'll move fully to 1.2 work this won't be necessary anymore, but > I'd like to beg one more month of effort to support this, unless it's > too much work. > > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
