That's fair and reasonable to me. We can discuss the SR4 option on our TSC meeting this week, and go ahead and get SR3 out the door. JamO

Honestly, given TSC's approval: AGREED: The TSC approves build 143 as the Fluorine SR3 build, pending CSIT jobs (abhijitk, 16:26:08) I would propose to just release SR3 and make it the TSC's

... and we're back in business: https://jenkins.opendaylight.org/releng/view/distribution/job/distribution-merge-managed-neon/ Thanks, Robert

AFAICT, this requires: - releasing odlparent-3.1.8 - creating version bump patches for all projects - releasing yangtools-2.0.21 - creating version bump patches for all projects - merging both sets of

Hi Frank, Looks like the eman jobs in Jenkins were removed due to project inactivity here: https://git.opendaylight.org/gerrit/80143 This is not a big deal. If the project is expected to continue

All, I am the project lead, and I believe sole committer at this point, of the eman project. This project has been inactive for some time, and besides an update I’d like to make, will remain so for

is this a cumbersome process for us? Like we've decided before with Fluorine SR3, since it's the last release for Fluorine maybe we take the time to make sure we get it as polished as possible. The

This is probably related to BC 1.61, quoting 1.62 release notes: A performance issue with RSA key pair generation that was introduced in 1.61 has been mostly eliminated. I am not sure it's worth

Same happened for https://jenkins.opendaylight.org/releng/job/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-fluorine/1526/ as well, In the middle of suite 9, login to karaf

I've was able to build and test a new Ubuntu 16.04 docker image which works with CSIT netconf jobs. https://git.opendaylight.org/gerrit/82523 Thanks, Anil

As I mentioned earlier, there has been some change in karaf fluorine so that now the first time you connect to the console via SSH (ssh -p 8101 karaf@....0.1) can take more than 10 secs. This produces

I've updated for controller, netconf, ovsdb, and yangtools. Luis, there seems to be some issues connecting to karaf console in the ofp jobs. Is that something you've seen from time to time? JamO

Just to be clear, it is not 3.2 we are asking, it is >=3.1. Robot 3.1.X is perfectly valid and compatible with both formats. BR/Luis

Faseela, It's not really mandatory for downstreams to upgrade to 3.2, but if they do not, the upstream int/test code will not work for them once the upstream moves ahead. So, downstreams could always

Luis, Why is it mandatory to update to robot 3.2 even for all downstream companies? Thanks, Faseela

Hello everyone, The Fluorine SR3 build candidate #143 is ready for testing [1.]. The distribution test job #448 [2.] is complete and the spreadsheet [3.] is updated with the CSIT results. Please sign

Thanks Anil!

Hi everybody, We have found some problem with robot version update: 1) Starting robot 3.1, there is a new syntax for FOR loops: *** Test Cases *** Example FOR ${element} IN

The issue is fixed with the latest global-jjb v0.38.4 update, which pulls in the fixes from lftools. The below change needs to be merged. https://git.opendaylight.org/gerrit/82516 Thanks, Anil

Ok we can pick 143 which is the next AR build to make sure that all the fixes are merged and vote tomorrow... thanks -- Daniel de la Rosa Customer Support Manager Lumina Networks Inc. e: