From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: glib: Update to 2.53.1.
Date: Mon, 22 May 2017 13:24:33 -0400 [thread overview]
Message-ID: <87lgpou7n2.fsf@netris.org> (raw)
In-Reply-To: <87d1b1yrzr.fsf@fastmail.com> (Marius Bakke's message of "Mon, 22 May 2017 14:51:20 +0200")
Marius Bakke <mbakke@fastmail.com> writes:
> Kei Kebreau <kei@openmailbox.org> writes:
>
>> kkebreau pushed a commit to branch gnome-updates
>> in repository guix.
>>
>> commit 90e0b6024b375f919878414163a6ad5857cc4b3e
>> Author: Kei Kebreau <kei@openmailbox.org>
>> Date: Sun May 21 18:15:00 2017 -0400
>>
>> gnu: glib: Update to 2.53.1.
>>
>> * gnu/packages/glib.scm (glib): Update to 2.53.1.
>
> Many (most?) of the GNOME-family packages follow an "even/odd"
> development cycle, where the stable branches have even minor versions.
> While I couldn't find it mentioned explicitly on the glib homepage, a
> peek in the git repository suggests that they follow this model:
>
> https://git.gnome.org/browse/glib/refs/
>
> So I think we should instead go for the most recent 2.52.x release.
> Can you check whether that is the case for "gobject-introspection" as
> well?
>
> `guix refresh` suggests the 1.52.x branch:
Yes, we should always use stable branches unless there is a compelling
reason to do otherwise.
Mark
next prev parent reply other threads:[~2017-05-22 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170521221928.10340.63400@vcs0.savannah.gnu.org>
[not found] ` <20170521221929.491B921037@vcs0.savannah.gnu.org>
2017-05-22 12:51 ` 01/01: gnu: glib: Update to 2.53.1 Marius Bakke
2017-05-22 17:24 ` Mark H Weaver [this message]
2017-05-23 1:26 ` Kei Kebreau
2017-05-23 15:01 ` Marius Bakke
2017-05-23 23:01 ` Kei Kebreau
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgpou7n2.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).