Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adrian Perez de Castro <aperez@igalia.com>
Cc: Thomas Devoogdt <thomas@devoogdt.com>,
	Thomas Devoogdt <thomas.devoogdt@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/webkitgtk: bump to version 2.37.1
Date: Mon, 5 Sep 2022 15:47:14 +0200	[thread overview]
Message-ID: <20220905154709.0e283da6@windsurf> (raw)
In-Reply-To: <20220905162007.GB3611398@kodama>

Hello Adrian,

On Mon, 5 Sep 2022 16:20:07 +0300
Adrian Perez de Castro <aperez@igalia.com> wrote:

> development releases. WebKit GTK (and WPE) follow the old-style GNOME
> versioning scheme:
> 
>   * If the second version number is odd, it's a development release.
>     - If the number is <90, it's unstable. Example: 2.37.1 is unstable.
> 	- If the number is >=90, it's a release candidate. Example: 2.37.90.
>   * If the second number is even, it's a stable release. Example: 2.38.0.
> 
> The versioning scheme is detailed here, too:
> 
>   https://wpewebkit.org/release/schedule/

This has come up many times for GNOME packages. Perhaps we should add a
comment above the <pkg>_VERSION variable which explains this?

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

      reply	other threads:[~2022-09-05 13:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 12:25 [Buildroot] [PATCH] package/webkitgtk: bump to version 2.37.1 Thomas Devoogdt
2022-09-05 13:20 ` Adrian Perez de Castro
2022-09-05 13:47   ` Thomas Petazzoni via buildroot [this message]

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=20220905154709.0e283da6@windsurf \
    --to=buildroot@buildroot.org \
    --cc=aperez@igalia.com \
    --cc=thomas.devoogdt@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=thomas@devoogdt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox