At Hal's suggestion, I've e-mailed the b2g release drivers list to find out the details about this contractual obligation. I'll keep the list updated once I find out more.
-Justin On Sun, Feb 10, 2013 at 11:33 AM, Hal Wine <[email protected]> wrote: > [dev-b2g to bcc] > On 2013-02-09 17:33 , Justin Lebar wrote: >> Hi, everyone. >> >> I'd like to ask the group if anyone has an objection to naming our b2g >> branches something like "b2g-vX_Y_Z" in gecko.git [1]. I think the >> simplest thing to do is probably to copy the name from the hg >> repository, but I don't feel strongly about the specifics, so long as >> the name has "b2g" in it. > [snip] >> John and/or Hal, can you please confirm that you received this message >> and will follow this scheme in the future? Thanks. > Process clarification: > > The decision on what branches are named in > git.mozilla.org:releases/gecko.git is not up to anyone on this thread, > although we can express our opinions of course. > > These branch names are part of the contractual agreement between Mozilla > Corporation and our FFOS partners. As such, FFOS product management and > release management would have to negotiate agreement with all partners > before any such change could be made. > > For better or worse, the existing branch names went through that > process, and RelEng implemented the business decision. Any proposed > change needs to follow the same process. > > --Hal > > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
