All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz@crc.id.au>
To: Lars Kurth <lars.kurth@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
	George Dunlap <dunlapg@umich.edu>,
	Julien Grall <julien.grall@linaro.org>,
	"committers@xenproject.org" <committers@xenproject.org>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen release cycle revisited
Date: Wed, 03 Jan 2018 02:07:48 +1100	[thread overview]
Message-ID: <1722077.KMArrVY7cK@wopr.lan.crc.id.au> (raw)
In-Reply-To: <371025E8-3FE9-47A5-A317-2C5088667A8B@citrix.com>


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

On Tuesday, 2 January 2018 11:54:43 PM AEDT Lars Kurth wrote:
> Hi Juergen:
> 
> thank you for raising this. As far as I can tell, the switch to the
> 6-monthly release model has had some consequences, some of which were
> predicted, others were not. So, I think we should probably review the
> decision. 
 
> Key concerns raised:
> • Too much work in actively maintaining 4 branches (6 security branches)
> • Impact on users (too many releases)
> • I think we are definitely incurring higher overheads than with longer
> cycles
 • It is not clear to me whether one of the key benefits – aka
> vendors getting patches into tree more easily – has in fact materialized •
> Better release predictability has materialized
> 
> Maybe the right approach would be to kick off some kind of survey to gather
> input from different stake-holders and maybe plan 4.11 for June. If there
> is a consensus for a change to say a year cadence, we probably wouldn’t
> execute this until 4.12 anyway. 

I would like to propose for consideration:

* 12 months between major releases (x.y)
* 3 or 4 months between point releases (x.y.z)

This way, we roll up all XSAs etc into a x.y.z release on a regular basis - 
which I believe would make the security teams job easier (let me know if I'm 
wrong with this?).

Then aim to release x.y+1 (or maybe x+1?) in, say, June each year.

I'm not sure if there has been a set time frame as a goal for x.y.z releases - 
from my not so close observations, they seem to be somewhat adhoc.

As always though - more than happy to get feedback / comments on the above.

-- 
Steven Haigh

📧 netwiz@crc.id.au       💻 http://www.crc.id.au
📞 +61 (3) 9001 6090    📱 0412 935 897

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2018-01-02 15:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  7:56 Xen release cycle revisited Juergen Gross
2017-12-14 11:28 ` Julien Grall
2017-12-14 11:38   ` Juergen Gross
2017-12-14 12:43     ` Julien Grall
2017-12-14 13:13       ` Juergen Gross
2017-12-15 14:54         ` Juergen Gross
2017-12-18 14:56           ` George Dunlap
2017-12-18 15:57             ` Julien Grall
2017-12-18 16:10               ` Juergen Gross
2017-12-18 16:38                 ` Julien Grall
2017-12-18 18:32                   ` Juergen Gross
2017-12-18 20:27                     ` Julien Grall
2017-12-19  6:58                       ` Juergen Gross
2017-12-19  8:47                         ` Jan Beulich
2017-12-19 10:42                           ` Steven Haigh
2017-12-19 11:44                             ` George Dunlap
2017-12-19 12:25                               ` Steven Haigh
2017-12-18 16:53                 ` George Dunlap
2017-12-14 14:07     ` Jan Beulich
2017-12-14 14:11 ` Jan Beulich
2017-12-18 15:48   ` George Dunlap
2018-01-02 12:54 ` Lars Kurth
2018-01-02 13:10   ` Juergen Gross
2018-01-02 15:07   ` Steven Haigh [this message]
2018-01-02 16:22     ` Jan Beulich

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=1722077.KMArrVY7cK@wopr.lan.crc.id.au \
    --to=netwiz@crc.id.au \
    --cc=JBeulich@suse.com \
    --cc=committers@xenproject.org \
    --cc=dunlapg@umich.edu \
    --cc=jgross@suse.com \
    --cc=julien.grall@linaro.org \
    --cc=lars.kurth@citrix.com \
    --cc=xen-devel@lists.xenproject.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.