15:06:43 #startmeeting carbon release sync 15:06:43 Meeting started Mon May 8 15:06:43 2017 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 15:06:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:06:43 The meeting name has been set to 'carbon_release_sync' 15:06:52 #topic recap 15:07:26 #info the biggest issue with Carbon was that Karaf 4 seemed to have wildly changed bundle/feature lifecycle managment from Karaf 3 and that would cause all kinds of problems 15:08:34 #info in particular, it reloads bundles and features in ways that Karaf 3 didn't, many (really, almost all) ODL bundles and features dont' handle being reloaded correctly, so pretty regularly a bundle will not come back and result in things just hanging 15:08:52 #info this happens with Karaf 4 SingelFeatureTests pretty regularly causing the autorelease to fail almost every time on those 15:09:09 #Info this has more dire implications when doing normal things with CSIT and installing feautre 15:10:15 #link https://lists.opendaylight.org/pipermail/release/2017-May/010746.html the result is that combined with a statement from Jamie that Karaf 3 will have security support for the duration of Carbon, people are thinking of shipping Carbon on Karaf 3 and moving to Karaf 4 as a major effort in Nitrogen 15:10:37 #info it looks like there are 7 +1s from TSC members to move Carbon to Karaf 3 15:21:14 #link https://docs.google.com/spreadsheets/d/1VcB12FBiFV4GAEHZSspHBNxKI_9XugJp-6Qbbw20Omk/edit#gid=1455372448 colindixon has been tracking autorelease failures here 15:30:07 #topic where we are 15:30:31 #info we have 3 autorelease jobs for carbon now: normal, failnever, and notest 15:44:57 #action zxiiro-away will work on consolidating those into one job that runs with -Dskip.karaf.featureTest=true for now and maybe a better way to disable Karaf 4 in the future 15:45:24 #action colindixon will close the thread with 7 +1s from TSC members on shipping Carbon on Karaf 3 asking for any critical feedback on the decisions 15:46:17 #action colindixon will follow up with a mail to relaese and TSC basically saying we should take the last succsessful staging repository and use it as RC0 and lock the stable/carbon branches to start making progress on testing and releasing Carbon 15:46:18 #endmeeting