From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: pango: update to 1.51.2, enable tests
Date: Fri, 23 Feb 2024 22:00:04 +0100 [thread overview]
Message-ID: <20240223210004.029B527209@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48712@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
There's a closed pull request on the void-packages repository
pango: update to 1.51.2, enable tests
https://github.com/void-linux/void-packages/pull/48712
Description:
@cinerea0
`pango` devs dropped even/odd versioning. `1.51.*` is considered stable now.
read the section `Versioning` (it was added 3 moths ago) of the `README.md` - https://gitlab.gnome.org/GNOME/pango
> Historically, Pango was following the traditionally even/odd library
versioning scheme where stable releases are marked by even minor
and development releases by an odd minor.
In recent years, Pango development has slowed down so much that it
no longer makes sense to have unstable cycles, or even unstable releases.
Going forward, pango versions will simply be increasing triples, with
no particular significance to the parity of the minor version.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl x
- armv7l x
- armv6l-musl x
prev parent reply other threads:[~2024-02-23 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 2:23 [PR PATCH] " chrysos349
2024-02-14 2:40 ` [PR PATCH] [Updated] " chrysos349
2024-02-23 21:00 ` cinerea0
2024-02-23 21:00 ` cinerea0 [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=20240223210004.029B527209@inbox.vuxu.org \
--to=cinerea0@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).