Vote: making BGPCEP a Release Integrated project


Robert Varga
 

And +1 from me as well.

This vote carries with 3 in favor, 2 not voted and no objects.

I will prepare a transition plan and execute it by the Phosphorus MRI
window.

Regards,
Robert

On 23/02/2021 08:48, Dana Kutenicsova wrote:
+1

-----Original Message-----
From: Robert Varga <nite@...>
Sent: Monday, February 22, 2021 5:20 PM
To: Claudio David Gasparini <claudio.gasparini@...>; Dana Kutenicsova <dkutenicsova@...>; Ajay Lele <ajayslele@...>; DUGEON Olivier IMT/OLN <olivier.dugeon@...>
Cc: app-dev@...
Subject: Vote: making BGPCEP a Release Integrated project

Hello everyone,

as you might be aware, I have been removing projects from autorelease and switching them to Release Integrated (as opposed to Snapshot
Integrated) lifecycle.

The gory details about the differences are documented here:
https://docs.opendaylight.org/en/latest/release-process/managed-release.html#managed-release-integrated-release-process,
but it all boils down to two things:

- the project is responsible for spinning its own release artifacts
- the project's downstream use its released versions, not SNAPSHOTs

In current (Silicon) Simultaneous Release cycle, both AAA and NETCONF are now MRI projects, which opens up the possibility for BGPCEP to do the same.

I am not aware of any benefits remaining Snapshot Integrated would bring to BGPCEP and would therefore transition BGPCEP to MRI as well.

To that effect, BGPCEP committers, please cast your vote in the usual
-1/0/+1 manner on the following question:

Do you approve BGPCEP becoming a Managed Release Integrated project?


Other community members are welcome to chime in as well :)

Thanks,
Robert






Claudio David Gasparini <claudio.gasparini@...>
 

+1

-----Original Message-----
From: Robert Varga <nite@...>
Sent: Monday, February 22, 2021 5:20 PM
To: Claudio David Gasparini <claudio.gasparini@...>; dkutenicsova@...; Ajay Lele <ajayslele@...>; DUGEON Olivier IMT/OLN <olivier.dugeon@...>
Cc: app-dev@...
Subject: Vote: making BGPCEP a Release Integrated project

Hello everyone,

as you might be aware, I have been removing projects from autorelease and switching them to Release Integrated (as opposed to Snapshot
Integrated) lifecycle.

The gory details about the differences are documented here:
https://docs.opendaylight.org/en/latest/release-process/managed-release.html#managed-release-integrated-release-process,
but it all boils down to two things:

- the project is responsible for spinning its own release artifacts
- the project's downstream use its released versions, not SNAPSHOTs

In current (Silicon) Simultaneous Release cycle, both AAA and NETCONF are now MRI projects, which opens up the possibility for BGPCEP to do the same.

I am not aware of any benefits remaining Snapshot Integrated would bring to BGPCEP and would therefore transition BGPCEP to MRI as well.

To that effect, BGPCEP committers, please cast your vote in the usual
-1/0/+1 manner on the following question:

Do you approve BGPCEP becoming a Managed Release Integrated project?


Other community members are welcome to chime in as well :)

Thanks,
Robert


Dana Kutenicsova <dkutenicsova@...>
 

+1

-----Original Message-----
From: Robert Varga <nite@...>
Sent: Monday, February 22, 2021 5:20 PM
To: Claudio David Gasparini <claudio.gasparini@...>; Dana Kutenicsova <dkutenicsova@...>; Ajay Lele <ajayslele@...>; DUGEON Olivier IMT/OLN <olivier.dugeon@...>
Cc: app-dev@...
Subject: Vote: making BGPCEP a Release Integrated project

Hello everyone,

as you might be aware, I have been removing projects from autorelease and switching them to Release Integrated (as opposed to Snapshot
Integrated) lifecycle.

The gory details about the differences are documented here:
https://docs.opendaylight.org/en/latest/release-process/managed-release.html#managed-release-integrated-release-process,
but it all boils down to two things:

- the project is responsible for spinning its own release artifacts
- the project's downstream use its released versions, not SNAPSHOTs

In current (Silicon) Simultaneous Release cycle, both AAA and NETCONF are now MRI projects, which opens up the possibility for BGPCEP to do the same.

I am not aware of any benefits remaining Snapshot Integrated would bring to BGPCEP and would therefore transition BGPCEP to MRI as well.

To that effect, BGPCEP committers, please cast your vote in the usual
-1/0/+1 manner on the following question:

Do you approve BGPCEP becoming a Managed Release Integrated project?


Other community members are welcome to chime in as well :)

Thanks,
Robert


Robert Varga
 

Hello everyone,

as you might be aware, I have been removing projects from autorelease
and switching them to Release Integrated (as opposed to Snapshot
Integrated) lifecycle.

The gory details about the differences are documented here:
https://docs.opendaylight.org/en/latest/release-process/managed-release.html#managed-release-integrated-release-process,
but it all boils down to two things:

- the project is responsible for spinning its own release artifacts
- the project's downstream use its released versions, not SNAPSHOTs

In current (Silicon) Simultaneous Release cycle, both AAA and NETCONF
are now MRI projects, which opens up the possibility for BGPCEP to do
the same.

I am not aware of any benefits remaining Snapshot Integrated would bring
to BGPCEP and would therefore transition BGPCEP to MRI as well.

To that effect, BGPCEP committers, please cast your vote in the usual
-1/0/+1 manner on the following question:

Do you approve BGPCEP becoming a Managed Release Integrated project?


Other community members are welcome to chime in as well :)

Thanks,
Robert