Re: [E] Re: Release Interview

Robert Varga

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

I was using this page ( 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:
as part of"silicon-mri",
just as

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.



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
> <> to pick up
> other tickets for netconf, etc.


> 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.


Join to automatically receive all group messages.