From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/network-manager: bump to version 1.33.1
Date: Fri, 16 Jul 2021 23:15:03 +0200 [thread overview]
Message-ID: <20210716231503.48f47eea@windsurf> (raw)
In-Reply-To: <20210716031025.1524809-1-james.hilliard1@gmail.com>
On Thu, 15 Jul 2021 21:10:25 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> +NETWORK_MANAGER_VERSION_MAJOR = 1.33
Isn't 1.33 a development branch/release ?
https://wiki.gnome.org/Projects/NetworkManager is not very clear when
it says "Major NetworkManager releases are numbered 1.y.0, with y being
an even number. For example, 1.0.0, 1.2.0, ..., 1.18.0. Minor stable
releases are numbered 1.y.z, with y and z being even numbers. For
example 1.4.2, 1.18.2.".
However, the NEWS file at
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/main/NEWS
says:
=============================================
NetworkManager-1.34
Overview of changes since NetworkManager-1.32
=============================================
This is a snapshot of NetworkManager development. The API is
subject to change and not guaranteed to be compatible with
the later release.
USE AT YOUR OWN RISK. NOT RECOMMENDED FOR PRODUCTION USE!
So they don't even mention 1.33.
Another point: as we're updating from 1.22 to 1.32 (potentially), is
just a simple bump sufficient? Aren't there new options/features that
should be taken into account ?
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-16 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 3:10 [Buildroot] [PATCH 1/1] package/network-manager: bump to version 1.33.1 James Hilliard
2021-07-16 21:15 ` Thomas Petazzoni [this message]
2021-07-16 21:43 ` Alexander Dahl
2021-07-16 21:43 ` Alexander Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210716231503.48f47eea@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox