I can create a branch off of RB16.04, once we have a name for the branch On Thu, Jul 7, 2016 at 1:51 PM, Daniel Mihai <[email protected]> wrote:
> My understanding is that Committers will be in the path even in a separate > branch. This might be a good time to propose someone from Affinegy to > become a SCL/Router Committer. That Committer would be responsible mainly > for merging the iOS changes – at least for now. > > > > I would prefer a separate branch for iOS, just in case something very > urgent will up for 16.04a before the iOS changes will be ready. > > > > Thanks, > > Dan > > > > *From:* Lioy, Marcello [mailto:[email protected]] > *Sent:* Thursday, July 7, 2016 1:42 PM > *To:* Josh Spain <[email protected]>; > [email protected]; Daniel Mihai < > [email protected]>; Ry Jones <[email protected]> > *Cc:* Kishore Kolli <[email protected]>; Jorge Martinez < > [email protected]> > *Subject:* RE: Branch for iOS changes > > > > + Dan & Ry > > > > I think we agreed to do it on a branch off of 16.04 so that we didn’t need > to worry about the committers getting in the path, particularly on the > release branch. I believe Ry also indicated it would be possible at the > very least to hand trigger verification builds, or (if possible) actually > have automatic verify builds on that branch. > > > > Dan, Ry, is that your recollection also? > > > > *From:* Josh Spain [mailto:[email protected] <[email protected]>] > *Sent:* Thursday, July 07, 2016 1:33 PM > *To:* Lioy, Marcello <[email protected]>; > [email protected] > *Cc:* Kishore Kolli <[email protected]>; Jorge Martinez < > [email protected]> > *Subject:* Branch for iOS changes > > > > Marcello and Core Team, > > > > Should we be pushing iOS changes to RB16.04 or should we create a feature > branch off of RB16.04 and push to it? > > > > Thanks, > > Josh > > *Josh Spain, Director of Engineering, Affinegy* > > 1705 S. Capital of Texas Hwy, Ste. 310, Austin, TX, 78746 > 512.535.1700 > [email protected] http://affinegy.com >
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
