integration-dev@lists.opendaylight.org

Home Messages Hashtags Subgroups

Messages

Between

and

Re: [opendaylight-dev][release] OpenDaylight - Phosphorus SR1

Hello, I have just successfully released TransportPCE for Phosphorus SR1 tagged with version 4.1.0. You can find the log output

By Christophe Betoule · #14563 ·

[opendaylight-dev][release] OpenDaylight - Phosphorus SR1

Hello All, OpenDaylight Phosphorus SR1 version bump is complete and the staging repository is being promoted. The 'stable/phosphorus' branch is unlocked. Pending activities required to be complete for

By Anil Belur · #14562 ·

Re: [E] Re: [integration-dev] integration/distribution version issues

I wasn't really questioning why there are two release tracks. Just that it would be nice and could be possible to make the process a little simpler & more automated to reduce confusion and potential

By Sangwook Ha · #14561 ·

Re: [E] Re: [integration-dev] integration/distribution version issues

Yes, Silicon SR3 has shown TCPE can easily manage being an MRI project. Unimgr is irrelevant, as they still work on kernel from a few years back. Regards, Robert

By Robert Varga · #14560 ·

Re: [E] Re: [integration-dev] integration/distribution version issues

Yes there is and there is quite a bit of history attached to that. Our governance clearly states that each project is independent, which in this context means is free to release whenever as well as

By Robert Varga · #14559 ·

Re: [E] Re: [integration-dev] integration/distribution version issues

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

By Daniel de la Rosa · #14558 ·

Re: [E] Re: [integration-dev] integration/distribution version issues

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

By Luis Gomez · #14557 ·

Re: [E] Re: [integration-dev] integration/distribution version issues

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

By Luis Gomez · #14556 ·

Re: integration/distribution version issues

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

By Luis Gomez · #14555 ·

Re: [E] Re: [integration-dev] integration/distribution version issues

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

By Sangwook Ha · #14554 ·

Re: [E] Re: [integration-dev] integration/distribution version issues

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

By Sangwook Ha · #14553 ·

Re: integration/distribution version issues

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

By Robert Varga · #14552 ·

Re: integration/distribution version issues

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

By Luis Gomez · #14551 ·

Re: integration/distribution version issues

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

By Robert Varga · #14550 ·

Re: integration/distribution version issues

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

By Daniel de la Rosa · #14549 ·

integration/distribution version issues

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

By Sangwook Ha · #14548 ·

Re: [it-infrastructure-alerts][notice] ODL maintenance window (11:00pm Sun, Nov 14 - 3:30am Mon, Nov 15 UTC)

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

By Anil Belur · #14547 ·

Re: [it-infrastructure-alerts][notice] ODL maintenance window (11:00pm Sun, Nov 14 - 3:30am Mon, Nov 15 UTC)

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

By Anil Belur · #14546 ·

Re: [opendaylight-dev][release] OpenDaylight - Silicon SR3 release status

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

By Luis Gomez · #14545 ·

Re: [opendaylight-dev][release] OpenDaylight - Silicon SR3 release status

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

By Robert Varga · #14544 ·

121 - 140 of 14683

Home Hashtags Subgroups Terms