AFAIK, TPCE is going to be managed from Sulfur or even Phosphorus so makes sense to consolidate to a single repo. -- Daniel de la Rosa ODL Release Manager

BTW below I meant "consolidate back to single distribution".

I think the part that is confusing is to have 2 distros so different (life-cycle, release, tagging, etc) in the same repo, I remember we did this long time back because we wanted to avoid having a new

Just 2 things: - The common distribution (opendaylight/pom.xml) has never been governed by auto-release or automatic bump for that matter, please recheck your links if you do not believe. Also the

Regarding the version mismatch for the common release, what I meant was for the karaf version in 'opendaylight/pom.xml' and the other versions - for example, release tag '14.3.0' would have the karaf

Looking at the release & version bump cycle, some of the steps may be simplified, and hopefully automated: - For each release of managed projects, release & version bump, are done separately a few

Three, actually. Yes, and therefore the release lifecycle of int/dist is unlike any other project I have come across. Right-o, but unfortunately you are explaining something completely off-topic, so

I thought this was clear, at least to ODL old folks, the int/dist project holds 2 distributions: - Karaf distribution (karaf/pom.xml) only containing Managed projects is also a Managed project and

This boils down to interaction between autorelease and int/dist. autorelease assumes branch cutting involves bumping minor version, which has been true for all MSI projects since forever. int/dist

Let me add more Robert and team to make sure that they see this email

It appears that the versions in integration/distribution/opendaylight have not been updated, and some Jenkins jobs are failing: e.g. openflowplugin-csit-1node-sanity-only-sulfur I submitted two

Hello all, ODL maintenance window is complete. All services are back online! Thank you for your patience. Regards, Anil

Hello all, We had an internal review on the estimates, and it's been advised we require a larger window than estimated (increased by 2 hours) since we have large volumes to be taken offline and moved

Thanks everyone, here is the distribution release: https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/opendaylight/14.3.0/ BR/Luis

Well, that's true, but then spinning a new release of a single project is quite straightforward, so TPCE can run as fast as kernel projects are integrated into int/dist -- it even could become an MRI

What: LF will perform maintenance on ODL services. When: 11:00pm Sun, Nov 14 - 3:30am Mon, Nov 15 UTC (10:00am Mon, Nov 15 - 2:30pm Mon, Nov 15 AEDT) Why: ODL Services (Jenkins, Nexus) some of LVM's

Thanks Luis, and in that case, please proceed to release Silicon SR3 at your earliest convenience Thank you all

The release actually happened before the other projects because TPCE does not depend anymore on MSI projects. For future, I would still recommend TPCE to wait for the TSC release approval, otherwise

HI Gilles, This is from the other email thread.... The logs you show below are for a normal merge job that does not publish release artifacts but SNAPSHOT. So in short, you have bumped TPCE to use

Hi Daniel, Shweta released TransportPCE SR3 last week. Please see the following log :https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/transportpce-release-merge/23/ At first