Date
1 - 11 of 11
[releng][TSC] phosphorus release status - master branch has been locked
|
Anil Belur
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 activities are complete, I will notify the status here. Regards, Anil Belur |
|
|
|
Anil Belur
On Tue, Sep 21, 2021 at 10:01 AM Anil Belur <abelur@...> wrote:
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 development, while the "stable/phosphorous" branch remains locked until the phosphorous release. New Jenkins jobs for the phosphorous stream will be added once the CR [1.] is merged. Regards, Anil Belur |
|
|
|
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 Anil, i think next release code name should be Sulfur Thanks On Mon, Sep 20, 2021 at 7:30 PM Anil Belur <abelur@...> wrote:
|
|
|
|
Anil Belur
On Tue, Sep 21, 2021 at 3:29 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
Yes, We need Luis or someone from the integration team to merge 97467, then we can pick up the subsequent AR build. |
|
|
|
On Tue, Sep 21, 2021 at 2:45 AM Anil Belur <abelur@...> wrote:
97467 is merged, so i guess i can pick AR #211, Integration #167. There are some CSIT failures so i guess we have to just evaluate that. @Anil Belur can you produce the spreadsheet for phosphorus? i dont have privileges to come up with a new one thanks |
|
|
|
Robert Varga
On 22/09/2021 06:14, Daniel de la Rosa wrote:
On Tue, Sep 21, 2021 at 2:45 AM Anil Belur <abelur@... <mailto:abelur@...>> wrote:I have retriggered the job, as the OVSDB/OFP test cases failed with: Waiting to initialize infrastructure...i.e. instance limits, again :( Bye, Robert |
|
|
|
On Wed, Sep 22, 2021 at 5:17 AM Robert Varga <nite@...> wrote: On 22/09/2021 06:14, Daniel de la Rosa wrote: 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 candidate
|
|
|
|
Robert Varga
On 21/09/2021 02:01, Anil Belur wrote:
Hello all,It seems Jenkins/JJB integration is busted. I have filed https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22956 for that. Bye, Robert |
|
|
|
Robert Varga
On 23/09/2021 18:24, Robert Varga wrote:
On 21/09/2021 02:01, Anil Belur wrote:To explain: it is failing since Sep 21, hence Jenkins jobs do not reflect Gerrit branches mapping:Hello all,It seems Jenkins/JJB integration is busted. I have filed https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-22956 for that. - all -phosphorus jobs still refer to master branch - there are no -sulfur jobs Regards, Robert |
|
|
|
On Thu, Sep 23, 2021 at 10:10 AM Robert Varga <nite@...> wrote: On 23/09/2021 18:24, Robert Varga wrote: it seems that the issue has been fixed by LF IT so are we good to pick up Phosphorus AR #216 integration #174 is showing some BGPCEP failed test cases bgpcep https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-throughpcep-all-phosphorus/172/ bgpcep https://jenkins.opendaylight.org/releng/job/bgpcep-csit-1node-userfeatures-all-phosphorus/172/ So I'm assuming that we do want to fix those?
|
|
|
|
Anil Belur
Hi Robert: The jjb-merge job failed since a new branch is added and the CR changes a lots of job configs. This translates to updating all the job configs on Jenkins and requires more time to complete. In most cases, I generally increase the timeout for the jjb-merge job during the branch cut (which I missed this time). PS note: This can be fixed by "remerge" comment on the CR. - Anil On Fri, Sep 24, 2021 at 3:10 AM Robert Varga <nite@...> wrote: On 23/09/2021 18:24, Robert Varga wrote: |
|
|