On Mon, Dec 2, 2019 at 12:49 PM Till Maas <till@redhat.com> wrote:
Hi,

Am Mo., 2. Dez. 2019 um 11:30 Uhr schrieb Edward Haas <edwardh@redhat.com>:

> Users of Nmstate in both development and user context need to track the Nmstate updates.
>
> The following points focus on RPM distribution and consumption.
> Nmstate users may switch between development and user consumption, depending on the individual project workflow and timelines.
> Therefore, the Nmstate distribution can be grouped into development and stable consumption.
>
> These are the different possible consumptions that may be required by Nmstate users (as repos):
> - Development
> -- Track master head.

How about we call this nmstate-git for automatic rebuilds of each
commit in the master branch.

That or nmstate-master-git to remove ambiguity, but I do not have a strong opinion on this.

> -- Track nmstate-0.1 stable branch head. (this branch should contain fixes for the 0.1 version)

nmstate-0.1-git for automatic rebuilds of each commit in the nmstate-0.1 branch.

ACK

> - Stable
> -- Track tagged releases for the 0.2 version.

I guess you mean releases tagged from the master branch? This would be
with manual rebuilds for now.

It is now on master and later on will branch out probably.
I'm fine with manual builds for stable releases.


IMHO this should be the "nmstate" Copr. We can prepare a command line
so it could be done easily whenever we release a new version. But for
this it would be beneficial to release versions more often than once
every three months.

We will release often as the QA teams will not consume anything else.
Only development teams may consume HEAD tracking COPR.

> -- Track tagged releases for the 0.1 version.

And this could be "nmstate-0.1" Copr with manual rebuilds for now.

What I do not yet understand is, will there be new releases from the
nmstate-0.1 branch? There were no releases from the stable_v0.0.8
branch which makes me wonder.

Yes, it will happen when backporting fixes from master to the stable 0.1 branch.


> When we move forward and need to focus on 0.3 release, then:
> - A branch will be created for nmstate-0.2 and we'll need to track its head for development context.
> - Add tracking of tagged releases for the 0.3 version.
>
> The above repos should be available for CentOS8+ and Fedora31+.
> Some as COPR and some as formal CentOS/Fedora.

In general, tagged releases will go into RHEL and then later into
CentOS but it will take some time. When CentOS stream is fully
operational, this will be faster. The tagged releases from master will
probably just be available in Fedora Rawhide etc. However, it is
unclear to me whether Fedora 31 will get new releases from the
nmstate-0.1 branch (if there will be releases) or from master.

I think we should release 0.1 fixes on Fedora.
It is up to us.
We have an interest to make it available for consumption as much as possible
and as stable as possible.


Kind regards
Till

--
Till Maas
He/His/Him
Ansible RHEL Networking System Role Maintainer

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Laurie Krebs, Michael O'Neill,
Thomas Savage