Dear releng/autorelease team, As far as I can see, the failure seems to repeat Bug 8342 but I can't say for sure with only the console output. Thus, I updated the spread sheet but left

Attention alto-devs, Autorelease carbon failed to build odl-alto-simpleird from alto in build 287. Attached is a snippet of the error message related to the failure that we were able to automatically

OK… I suspect that there are issues which occasionally make SFT hang—mostly in autorelease—that I don't understand: https://lists.opendaylight.org/pipermail/release/2017-May/010490.html I'm

Colin, I have just finished a build of alto project on my machine and it completes successfully. The features4-alto takes about 1:30 minutes. Hope that helps. Regards,

I have no idea. Is it possible a temporary issue? I'm testing it on my local machine. Best, Jensen

Colin, I'll look into this. Thanks for the notification! Regards, Kai On 05/01/2017 09:52 AM, Colin Dixon wrote:

See here: https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-failnever-carbon/3/ ALTO devs, please comment if you can. Cheers, --Colin

Jensen and Shaw, Can you take some time and test the boron release? Thanks! Regards, Kai -------- Forwarded Message

Thanks Kai, I failed to notice that. On the other hand, better be safe than sorry :) Regards, Robert

Good to know! Hope everything goes well! By the way, I checked the latest patch and the affected feature project is not included in the default build cycle so it

Thanks Kai, I have restarted the Boron SR3 respin with this build: https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/233/ Cheers, Thanh

Hi Thanh Ha, I have reviewed the patch. Thanks for the notice. Regards, Kai On

Attention alto-devs, Can we get someone to review and +2 the alto patch asap? We'd like to get a Boron SR3 respin going as soon as possible. Thanks, Thanh

Hi Mike, I confirm the migration to Karaf 4 has not raised any issue or concern. Thanks for the notice. Regards, Kai

ALTO M5 Status 1. Please provide updates on any previously-incomplete items from prior milestone readouts. No incomplete items. 2. Has your project met code freeze, i.e., only bug fixes are allowed

Based on our analysis, your project has completed Karaf 4 Migration as part of the Carbon Simultaneous Release with no additional action items pending. Please confirm the status of your Karaf 4

ALTO 1. Please provide updates on any previously-incomplete items from prior milestone readouts. N/A 2. Has your project achieved API freeze such that all externally accessible Stable or

Hi Katie, I'm very sorry we didn't catch the date. I'll submit the status report by tomorrow. Thanks! Regard, Kai On 03/07/2017 04:27 PM, Katie Zhang

Hi Kai: Your Project is missing the M4 status report , can you please submit some as soon as possible? thanks a lot. -- Best katie

Thanks Kai, Jensen for fixing this issue.