all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>, Carlo Zancanaro <carlo@zancanaro.id.au>
Subject: Re: We need an RFC procedure [Re: Services can now have a default value]
Date: Mon, 22 May 2017 18:45:11 -0400	[thread overview]
Message-ID: <20170522224511.GD11317@jasmine> (raw)
In-Reply-To: <877f18bn78.fsf@elephly.net>

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

On Mon, May 22, 2017 at 11:23:23PM +0200, Ricardo Wurmus wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
> > What would be stable in the “stable branch”, packages or Guix?  :-)
> >
> > A branch where Guix itself is stable would be nice, though it would need
> > careful merging from master regularly.
> 
> This would make sense.  It would require some restraint in moving
> packages to different modules or breaking some underlying package
> features, which would cause ABI breakage.
> 
> I do think it would be possible, though.

It's definitely possible, but I'd like to see it proposed in more detail
by the group that will maintain it. It's not okay to start a "stable
branch" unless it will be properly supported.

> 
> > A branch where packages are stable (à la Debian stable) would be too
> > much work (I’m even skeptical it makes any sense given that many
> > declared and undeclared security vulnerabilities get patched everytime a
> > piece of software is released…).
> 
> Yeah, that wouldn’t make sense.  It’s hard enough to deal with security
> issues in current software in a timely fashion.

+1

Anyone who really needs this has a business use case that can support a
private fork, in my opinion.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-05-22 22:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-15 22:51 Services can now have a default value Ludovic Courtès
2017-04-15 23:11 ` ng0
2017-04-17 11:56   ` Ricardo Wurmus
2017-04-19 23:22     ` ng0
2017-04-20  8:53       ` Ricardo Wurmus
2017-04-20  9:09         ` ng0
2017-04-23 10:23           ` Ricardo Wurmus
2017-04-17 11:58 ` Ricardo Wurmus
2017-04-19 14:42 ` Carlo Zancanaro
2017-04-19 15:18   ` ng0
2017-04-19 21:20   ` Ludovic Courtès
     [not found]     ` <8737d32abz.fsf@zancanaro.id.au>
2017-04-20  8:42       ` Ludovic Courtès
2017-04-20 10:19         ` Carlo Zancanaro
2017-04-21 22:04           ` Ludovic Courtès
2017-04-21 23:41             ` Carlo Zancanaro
2017-04-22  0:46               ` We need an RFC procedure [Re: Services can now have a default value] ng0
2017-04-22  7:12                 ` Ricardo Wurmus
2017-04-22 10:08                   ` ng0
2017-04-22 22:55                     ` Ludovic Courtès
2017-04-23 10:13                       ` Ricardo Wurmus
2017-04-23 12:02                         ` ng0
2017-04-27 13:29                         ` Ludovic Courtès
2017-04-27 16:37                           ` Petter
2017-05-02 12:42                             ` Ludovic Courtès
2017-05-22 21:23                               ` Ricardo Wurmus
2017-05-22 22:45                                 ` Leo Famulari [this message]
2017-04-23 11:52                       ` ng0
2017-05-13 10:39               ` Services can now have a default value Carlo Zancanaro
2017-05-13 22:53                 ` Carlo Zancanaro
2017-05-15 12:48                   ` Ludovic Courtès
2017-04-22 14:46             ` Christopher Allan Webber
2017-04-22 14:59               ` Jan Nieuwenhuizen
2017-04-22 22:57               ` Ludovic Courtès

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=20170522224511.GD11317@jasmine \
    --to=leo@famulari.name \
    --cc=carlo@zancanaro.id.au \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.