Dear kenny We have created branch release-1.1.0 already for onap/cli and setup the Jenkins jobs as well.
This is done on the same commit as release binaries are done. Regards Kanagaraj M From: TIMONEY, DAN To: Kenny Paul<kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Cc: Jeremy Phelps<jphe...@linuxfoundation.org<mailto:jphe...@linuxfoundation.org>>;onap-tsc<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>> Subject: Re: [onap-tsc] Amsterdam Branching Timeline Time: 2017-11-17 04:04:28 Kenny, Excellent - what service! Thanks much, Dan Sent from MyOwn, an AT&T BYOD solution. ________________________________ From: "Kenny Paul" <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>> Date: Thursday, November 16, 2017 at 5:08:06 PM To: "TIMONEY, DAN" <dt5...@att.com<mailto:dt5...@att.com>> Cc: "onap-tsc" <onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>, "Jeremy Phelps" <jphe...@linuxfoundation.org<mailto:jphe...@linuxfoundation.org>> Subject: Re: [onap-tsc] Amsterdam Branching Timeline Hi Dan, yes the LF will handle that. Best Regards, -kenny Kenny Paul, Technical Program Manager kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> 510.766.5945 On Nov 16, 2017, at 1:22 PM, TIMONEY, DAN <dt5...@att.com<mailto:dt5...@att.com>> wrote: Kenny, After the release branches are created, we’ll also need to create new Jenkins jobs to compile against the new release branch. Is that the responsibility of each project team, or was LF planning to handle that?
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
