unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: core-updates merged!
Date: Wed, 26 Mar 2014 16:46:25 +0100	[thread overview]
Message-ID: <87txal0xpq.fsf@gnu.org> (raw)
In-Reply-To: <87mwgn8twp.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 18 Mar 2014 15:26:30 +0100")

I’ve just merged core-updates in master, and Hydra has already built
most of it.  So that brings glibc 2.19, grep 2.18, libgc 7.4, guile
2.0.11, bash 6.3, the ability to use directories as package sources
(instead of tarballs), and a bunch of other updates and improvements.

It’s been more than 3 months between this merge and the previous one,
which is probably too much.

To avoid lingering branches, I think we should have a more formal,
time-based process.  For instance, we would let the branch live for N
months exactly, and freeze it at N months minus one week.

GCC and glibc are released roughly every 6 months, but typically with a
3 month offset.  So I would go for N = 2 or N = 3.  Maybe N = 2 is
better as it would allow us to make core improvements and small upgrades
more often.

Thoughts?

Thanks,
Ludo’.

  reply	other threads:[~2014-03-26 15:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 14:26 core-updates merge soon! Ludovic Courtès
2014-03-26 15:46 ` Ludovic Courtès [this message]
2014-03-26 15:55   ` core-updates merged! Thompson, David
2014-03-26 16:14     ` Ludovic Courtès
2014-03-26 17:28       ` Thompson, David
2014-03-27  9:37         ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2015-01-05 16:51 core-updates, wip-armhf, and 0.8.1 Ludovic Courtès
2015-01-16 12:39 ` core-updates merged! Ludovic Courtès
2015-02-10 16:38 Federico Beffa
2015-02-10 18:46 ` Andreas Enge
2015-02-10 18:50   ` John Darrington
2015-02-10 19:38   ` Federico Beffa
2016-08-01  8:19 Core-updates Andreas Enge
2016-08-01 21:48 ` core-updates merged! Ludovic Courtès
2016-08-02 13:26   ` ng0
2016-08-02 17:32     ` Ludovic Courtès
2016-08-02 17:48       ` Leo Famulari
2016-08-02 21:28         ` Ludovic Courtès
2016-08-03  4:04           ` Leo Famulari
2016-08-03 16:42             ` Ludovic Courtès
2016-08-03 17:24               ` Leo Famulari
2016-08-03 17:56                 ` Ludovic Courtès
2016-08-03 18:39                   ` Leo Famulari
2016-08-03 20:01                     ` Ludovic Courtès
2016-08-03 21:01                       ` Leo Famulari
2016-08-03 21:27                         ` Andreas Enge
2016-08-03 22:14                           ` Leo Famulari
2016-08-06 14:42             ` Leo Famulari
2016-08-10 19:49               ` Leo Famulari
2016-08-13  7:15                 ` Manolis Ragkousis
2016-08-09  3:07           ` Leo Famulari
2017-08-18 21:24 'core-updates' status Marius Bakke
2017-08-21 21:07 ` Marius Bakke
2017-08-25 18:34   ` Marius Bakke
2017-08-25 19:55     ` Leo Famulari
2017-08-26 12:04       ` Ludovic Courtès
2017-08-26 13:30         ` core-updates merged! Marius Bakke
2017-08-27 16:03           ` Ludovic Courtès
2020-05-08 19:47 Marius Bakke
2020-05-08 20:48 ` Jack Hill

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=87txal0xpq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.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.
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).