TSC@lists.opendaylight.org

Home Messages Hashtags Subgroups

Messages

Between

and

Re: [releng][TSC] phosphorus release status - master branch has been locked

Phosphorus AR#212 integration #169 has only one test case failed bgpcep https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/167/ so looks to me like a good RC

By Daniel de la Rosa · #13853 ·

Re: [releng][TSC] phosphorus release status - master branch has been locked

I have retriggered the job, as the OVSDB/OFP test cases failed with: i.e. instance limits, again :( Bye, Robert

By Robert Varga · #13852 ·

Re: [releng][TSC] phosphorus release status - master branch has been locked

97467 is merged, so i guess i can pick AR #211, Integration #167. There are some CSIT failures

By Daniel de la Rosa · #13851 ·

Re: [release] Phosphorus Code Freeze for formal release

Sure, I think I caught up with int/dist and int/test pending patches, let me know if something is missing review/merge. BR/Luis

By Luis Gomez · #13850 ·

Re: [release] Phosphorus Code Freeze for formal release

So stable/phosphorus should be okay (once jobs are populated), but sulfur needs https://git.opendaylight.org/gerrit/c/integration/distribution/+/97582 merged. Luis, can you take a look,

By Robert Varga · #13849 ·

Re: [release] Phosphorus Code Freeze for formal release

So aside from the CSIT updates we'll also need an updated bgpcep release because we have busted BMP server-side and all test tools. bgpcep-0.16.5 is being promoted now to address these

By Robert Varga · #13848 ·

Re: [releng][TSC] phosphorus release status - master branch has been locked

Yes, We need Luis or someone from the integration team to merge 97467, then we can pick up the subsequent AR build.

By Anil Belur · #13847 ·

Re: [releng][TSC] phosphorus release status - master branch has been locked

Thanks Anil. Robert, please correct me if I'm wrong, but we have to wait for [1] to be fixed before we can pick a RC [1] https://git.opendaylight.org/gerrit/c/integration/test/+/97467 Anil, i think

By Daniel de la Rosa · #13846 ·

[releng][TSC] Decommision Nexus Log sever from Oct 1st, 2021.

Hello all, Presently, all of our CI job logs are shipped and stored on AWS S3 bucket [1.] and on Nexus2 Log server [2.]. We have been shipping/storing logs on the AWS S3 bucket, since this was enabled

By Anil Belur · #13845 ·

Re: [releng][TSC] phosphorus release status - master branch has been locked

Hello all, The version bump is complete, the master branch is promoted to the next release (Sulfer) and the "stable/phosphorous" branch is created. The master branch is unlocked and is open for

By Anil Belur · #13844 ·

[releng][TSC] phosphorus release status - master branch has been locked

Hello all, The master branch is locked for Phosphorus code freeze and branch cutting ("stable/phosphorus") and master branch will be promoted to next (Sulphur). Once the version bump and the release

By Anil Belur · #13843 ·

Phosphorus release, input to marketing

Hello TSC and all As we agree, I have updated the filters on this page. https://wiki.opendaylight.org/display/ODL/Phosphorus+Release to try to capture the bug fixes and enhancements for each of the

By Daniel de la Rosa · #13842 ·

Re: [ODL Discuss] LFx OpenDaylight Chat beta

I am meeting with the team next week on Wednesday. I'll try to get some more specifics and pass on the current feedback. Best, Casey Cain Senior Technical Community Architect Linux

By Casey Cain · #13841 ·

Re: [ODL Discuss] LFx OpenDaylight Chat beta

FYI I installed the recommended app and did not work either. We probably need Casey to show how this works tomorrow.

By Luis Gomez · #13840 ·

Re: [release] Phosphorus Code Freeze for formal release

Yes, the failures are caused by int/test's libraries not being able to deal with the new Entity Ownership Service implementation. Tomas is working on fixing that here:

By Robert Varga · #13839 ·

Re: [ODL Discuss] LFx OpenDaylight Chat beta

Hi All, Same for me too. Failed to join roomNo known server. BR Manoj On Tue, Sep 14, 2021 at 3:37 PM Guillaume Lambert via lists.opendaylight.org <guillaume.lambert=orange.com@...> wrote:

By manoj chokka · #13838 ·

Re: [release] Phosphorus Code Freeze for formal release

I believe that Robert is fully aware of this issue and working on it but I’m going to let him confirm it Thanks

By Daniel de la Rosa · #13837 ·

Re: [release] Phosphorus Code Freeze for formal release

Looks like we have a regression on bgpcep: https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/ BR/Luis

By Luis Gomez · #13836 ·

TSC Meeting for September 16, 2021 at 10 pm Pacific

Hello OpenDaylight Community, Next TSC meeting is September 2, 2021 at 10 pm Pacific Time. The agenda proposal and the connection details for this meeting are available at the following

By Guillaume Lambert · #13835 ·

Phosphorus Code Freeze for formal release

Hello TSC and all We are going to code freeze Phosphorus for all Managed Projects ( cut and lock release branches ) on Monday September 20th at 10 am pst Please remember that we only allow blocker bug

By Daniel de la Rosa · #13834 ·

581 - 600 of 14433

Home Hashtags Subgroups Terms