All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: xen-devel@lists.xen.org
Subject: Re: Notes from Xen BoF at Debconf15
Date: Tue, 8 Sep 2015 09:52:35 -0500	[thread overview]
Message-ID: <55EEF633.8090203@cardoe.com> (raw)
In-Reply-To: <55EEDAB102000078000A0B3B@prv-mh.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1309 bytes --]

On 9/8/15 5:55 AM, Jan Beulich wrote:
>>>> On 08.09.15 at 12:49, <Ian.Jackson@eu.citrix.com> wrote:
>> Jan Beulich writes ("Re: [Xen-devel] Notes from Xen BoF at Debconf15"):
>>> Right - 4.4.3 already was released with just one RC, and indeed I
>>> meant to stay with that model considering the little (if any) feedback
>>> we get on these RCs. I personally could live without doing any RCs,
>>> but [...]
>>
>> Having had the chance to reflect I am convinced that we should stop
>> doing RCs for point releases.
>>
>>> [I] thought so far that doing at least one kind of publicly indicates
>>> the intention of doing a release soon.
>>
>> You might hope that it would have that effect, but I don't think it is
>> working.  Also, if it does work, all it does is generate more patches,
>> making the `rc' more of a `prod to get your stuff shoveled in'.
> 
> Well, okay - no RCs anymore then unless someone offers a
> convincing reason to have them.
> 
> Jan
> 

So I'll just toss in a late thumbs up here. For libvirt we maintain
stable branches that are mostly just security fixes and other important
fixes. We tag these will without RCs and all the downstream distros (and
myself as the downstream maintainer for 3 distros) are happy with that
situation.

-- 
Doug Goldstein


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

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-09-08 14:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08  9:24 Notes from Xen BoF at Debconf15 Ian Campbell
2015-09-08  9:41 ` On distro packaging of stub domains (Re: Notes from Xen BoF at Debconf15) Ian Campbell
2015-09-08 15:03   ` Antti Kantee
2015-09-08 16:15     ` Ian Campbell
2015-09-08 16:26       ` Samuel Thibault
2015-09-08 16:37         ` Ian Campbell
2015-09-08 17:09           ` Samuel Thibault
2015-09-08 18:38       ` Antti Kantee
2015-09-09 11:15         ` Ian Campbell
2015-09-09 13:42           ` Antti Kantee
2015-09-08  9:47 ` Notes from Xen BoF at Debconf15 Jan Beulich
2015-09-08 10:15   ` Lars Kurth
2015-09-08 10:15   ` Ian Campbell
2015-09-08 10:39     ` Jan Beulich
2015-09-08 10:49       ` Ian Jackson
2015-09-08 10:55         ` Jan Beulich
2015-09-08 14:52           ` Doug Goldstein [this message]
2015-09-08 14:49 ` Doug Goldstein
2015-09-08 15:24   ` Ian Campbell
2015-09-17 10:06   ` George Dunlap
2015-09-16 13:20 ` Ian Campbell
2015-10-05 15:37 ` Ian Campbell

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=55EEF633.8090203@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=xen-devel@lists.xen.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 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.