[E] Re: Release Interview


Robert Varga
 

On 25/03/2021 17:18, navid.ghazisaidi@verizon.com wrote:
Thanks Robert!

I was using this page (https://docs.opendaylight.org/projects/integration-distribution/en/latest/platform-versions.html) which just shows the targeted release number but as you mentioned it didn't cover all previous versions.
Yes, because that page is end-user collateral for Simultaneous Release.
As such, it is updated during each MRI bump. For example in Silicon, the
first update was here:
https://git.opendaylight.org/gerrit/c/integration/distribution/+/92972/4/docs/platform-versions.rst
as part of https://git.opendaylight.org/gerrit/q/topic:"silicon-mri",
just as
https://git.opendaylight.org/gerrit/c/docs/+/92934/3/docs/release-notes/upgrade-process.rst
was.

This sort of thing happens in every release between "Release Integrated
Deadline" and "Version Bump Checkpoint".

How about other projects? If you agree we should start mapping them to
the main release version (in this case silicon)? I remember we discussed
this before but can you help me recall the reason why we can't use the
main release name for MRI projects?

Quick answer to that is: because MRI projects are released way before
Simultaneous Release. As an example: Silicon is not released yet, but
yangtools-6.0.0 was released on October 8th, 2020.

The entire idea of a monolithic autorelease-based Simultaneous Release
(where you build all the projects and release them at the same time)
does not actually have a basis in our governance and has been introduced
as a reaction to, and a stop-gap solution for, how badly our very first
release (Hydrogen) went. That in turn was a result of us having been
SNAPSHOT-integrated across all projects and our pom.xml being a horrible
mess. Neither of those is true anymore.

Regards,
Robert


Thanks,
Navid


On 3/25/21, 3:24 AM, "Robert Varga" <nite@hq.sk> wrote:

On 25/03/2021 06:14, navid.ghazisaidi@verizon.com wrote:
> All,
>
>
>
> I just updated the filters of
> https://wiki.opendaylight.org/display/ODL/Silicon+Release
> <https://wiki.opendaylight.org/display/ODL/Silicon+Release> to pick up
> other tickets for netconf, etc.

Thanks.

> Note that for some project (e.g., ODL parent, YANG tools, and
> infrautils) I don’t see any results, not sure if there is any jira
> ticket that I can’t capture it or there is nothing…

The reason for that is that the filter needs to include *all* versions
of MRI projects as integrated into int/dist at the time of release, i.e.
the filter for odlparent is not 'is 8.1.1', but rather (as of this
writing) 'in [8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.1.0, 8.1.1]'.

For obvious reasons I am not willing to maintain the list of versions
anywhere but a git repository.

Regards,
Robert



Daniel de la Rosa
 

I'll try to join as well. Adding TSC mailing list as requested

Thanks

On Fri, Mar 26, 2021 at 10:31 AM <guillaume.lambert@...> wrote:

Hi Casey

 

I am glad we agree to say we need to refine this process.

I can join during the Monday TWS slot. And I’ll do my best to compile something before.

Though, I am pretty sure we won’t have every input by this date.

 

Best Regards

Guillaume

 

 

De : Casey Cain [mailto:ccain@...]
Envoyé : jeudi 25 mars 2021 19:09
À : navid.ghazisaidi@...
Cc : Robert Varga; Daniel de la Rosa; Luis Gomez; LAMBERT Guillaume TGI/OLN; Brandon Wick
Objet : Re: [E] Re: Release Interview

 

After today's discussion on building the release marking info, can we sync at the next TWS meeting?

Would we be able to have all of the necessary pages up to date at that point and then we can focus on the interview?

 

I agree that we need to refine our reporting process to ensure that it is built into the release, but for Silicon, this manual process will have to do with our timeframe. 

 

Best,

Casey Cain

Technical Program Manager / Community Architect

Linux Foundation

_________________

IRC: CaseyLF

WeChat: okaru6

Voice: +1.408.641.0193

 

 

On Thu, Mar 25, 2021 at 9:18 AM <navid.ghazisaidi@...> wrote:

Thanks Robert!

I was using this page (https://docs.opendaylight.org/projects/integration-distribution/en/latest/platform-versions.html) which just shows the targeted release number but as you mentioned it didn't cover all previous versions. How about other projects? If you agree we should start mapping them to the main release version (in this case silicon)? I remember we discussed this before but can you help me recall the reason why we can't use the main release name for MRI projects?

Thanks,
Navid


On 3/25/21, 3:24 AM, "Robert Varga" <nite@...> wrote:

    On 25/03/2021 06:14, navid.ghazisaidi@... wrote:
    > All,
    >
    > 
    >
    > I just updated the filters of
    > https://wiki.opendaylight.org/display/ODL/Silicon+Release
    > <https://wiki.opendaylight.org/display/ODL/Silicon+Release> to pick up
    > other tickets for netconf, etc.

    Thanks.

    > Note that for some project (e.g., ODL parent, YANG tools, and
    > infrautils) I don’t see any results, not sure if there is any jira
    > ticket that I can’t capture it or there is nothing…

    The reason for that is that the filter needs to include *all* versions
    of MRI projects as integrated into int/dist at the time of release, i.e.
    the filter for odlparent is not 'is 8.1.1', but rather (as of this
    writing) 'in [8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.1.0, 8.1.1]'.

    For obvious reasons I am not willing to maintain the list of versions
    anywhere but a git repository.

    Regards,
    Robert


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.