From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Cc: Michel Alex <Alex.Michel@wiedemann-group.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/libzenoh-c: bump to version 0.11.0
Date: Wed, 10 Jul 2024 23:16:46 +0200 [thread overview]
Message-ID: <20240710231646.3299b8f2@windsurf> (raw)
In-Reply-To: <7e24df50-3710-4700-a644-901528a1a939@mind.be>
On Thu, 20 Jun 2024 18:03:57 +0200
Arnout Vandecappelle via buildroot <buildroot@buildroot.org> wrote:
> > -LIBZENOH_C_VERSION = 0.11.0.3
> > +LIBZENOH_C_VERSION = 0.11.0
>
> Does 0.11.0 come _after_ 0.11.0.3? I.e. should the final .3 be interpreted as
> something like a -rc3? This is very counter-intuitive... And it breaks
> release-monitoring.org...
Yes, 0.11.0 came *after* 0.11.0.3.
See https://github.com/eclipse-zenoh/zenoh-c/releases, which clearly
documents the following releases (in reverse chronological order):
0.11.0
0.11.0.3
0.11.0.2
v0.10.1-rc
v0.10.0-rc
No way one can write an algorithm that figures out which release is
newer than the other :-)
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-07-10 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 9:25 [Buildroot] [PATCH 1/2] package/libzenoh-c: bump to version 0.11.0 Michel Alex
2024-06-20 16:03 ` Arnout Vandecappelle via buildroot
2024-06-21 5:38 ` Michel Alex
2024-07-10 21:16 ` Thomas Petazzoni via buildroot [this message]
2024-07-10 21:23 ` Thomas Petazzoni via buildroot
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=20240710231646.3299b8f2@windsurf \
--to=buildroot@buildroot.org \
--cc=Alex.Michel@wiedemann-group.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.