unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: New release soon?
Date: Fri, 16 Nov 2018 23:03:58 +0100	[thread overview]
Message-ID: <20181116230358.1ef639a7@alma-ubu> (raw)
In-Reply-To: <87wopcsoro.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

On Fri, 16 Nov 2018 22:20:27 +0100
ludo@gnu.org (Ludovic Courtès) wrote:

> Heya,
> 
> Ricardo Wurmus <rekado@elephly.net> skribis:
> 
> >> Initially I thought we may want to wait for core-updates to be
> >> merged, but it looks like we have troubles focusing on that ;-),
> >> so I don’t know.  Thoughts?  
> >
> > I would prefer to have core-updates in the next release.  This has
> > been delayed for much too long.  This would also avoid the bad look
> > for a new release to have somewhat outdated core packages.
> >
> > If we can’t get core-updates ready within the next few weeks I won’t
> > object to a release without it, but I think we should really try.  
> 
> Yes, that makes sense to me.
> 
> So everyone: let’s join forces and get ‘core-updates’ finally merged!

What is to do for core-updates to succeed? Is it "just" that
hydra/berlin need to build it, or is there anything a human being can
do (Or is the former necessary to define the latter?)?

Is there a list of open/unresolved tasks?

Björn

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-11-16 22:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14  8:28 New release soon? swedebugia
2018-11-14 11:44 ` Ricardo Wurmus
2018-11-14 17:57   ` Marius Bakke
2018-11-16 18:10     ` Ludovic Courtès
2018-11-16 21:15       ` Ricardo Wurmus
2018-11-16 21:20         ` Ludovic Courtès
2018-11-16 22:03           ` Björn Höfling [this message]
2018-11-17  0:58             ` Gábor Boskovits
2018-11-17 14:14             ` Getting ‘core-updates’ merged Ludovic Courtès
2018-11-22  9:41               ` Ludovic Courtès
2018-11-22 19:54                 ` Björn Höfling
2018-11-23 13:52                 ` Ludovic Courtès
2018-11-23 21:44                   ` Julien Lepiller
2018-11-24  9:19                   ` Danny Milosavljevic
2018-11-25 15:54                     ` Ludovic Courtès
2018-11-26 17:59                       ` Danny Milosavljevic
2018-11-26 18:18                     ` Danny Milosavljevic
2018-11-28 10:46                       ` Ludovic Courtès
2018-11-26 17:54                 ` Björn Höfling

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=20181116230358.1ef639a7@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).