From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Lars Kurth <lars.kurth.xen@gmail.com>,
xen devel <xen-devel@lists.xenproject.org>,
community.manager@xenproject.org
Subject: Re: [xen 4.6 retrospective] More public/easy to find information about the release schedule
Date: Mon, 10 Aug 2015 17:32:04 +0200 [thread overview]
Message-ID: <1439220724.24583.14.camel@citrix.com> (raw)
In-Reply-To: <55C4D099.8030808@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 997 bytes --]
On Fri, 2015-08-07 at 17:36 +0200, Roger Pau Monné wrote:
> = Issue / Observation =
>
> The information about the release schedule is not clearly published
> anywhere apart from the mailing lists, which makes it hard for
> non-developers (or even for developers) given that the mailing list
> traffic for xen-devel is high.
>
> = Possible Solution / Improvement =
>
> Publish the release schedule in a web page with a concrete schedule,
> like the FreeBSD Release Engineering Team does:
>
> https://www.freebsd.org/releng/
>
+1
At Fedora, they do something similar:
https://fedoraproject.org/wiki/Releases/23/Schedule
https://fedoraproject.org/wiki/Releases/22/Schedule?rd=Releases/22
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-08-10 15:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 12:52 [xen 4.6 retrospective] Kicking off a retrospective for Xen 4.6 (deadline August 28th) Lars Kurth
2015-08-05 9:22 ` [xen 4.6 retrospective] [urgent] rename "freeze" window and make release branch as soon as possible after RC1 Lars Kurth
2015-08-06 10:52 ` Stefano Stabellini
2015-08-12 7:35 ` Jan Beulich
2015-09-02 11:50 ` Lars Kurth
2015-09-02 12:32 ` Jan Beulich
2015-09-02 13:12 ` Stefano Stabellini
2015-09-02 16:40 ` Lars Kurth
2015-08-06 11:25 ` Wei Liu
2015-08-07 10:57 ` Roger Pau Monné
2015-08-12 7:32 ` Jan Beulich
2015-08-07 15:36 ` [xen 4.6 retrospective] More public/easy to find information about the release schedule Roger Pau Monné
2015-08-10 8:33 ` Wei Liu
2015-08-10 9:06 ` Lars Kurth
2015-08-10 9:40 ` Fabio Fantoni
2015-08-10 12:32 ` Lars Kurth
2015-08-10 15:32 ` Dario Faggioli [this message]
2015-08-12 8:00 ` [xen 4.6 retrospective] [bad] review load near freeze point Jan Beulich
2015-08-12 11:34 ` Lars Kurth
2015-08-28 15:05 ` Lars Kurth
2015-08-28 15:21 ` Jan Beulich
2015-08-28 16:04 ` Lars Kurth
2015-08-28 16:22 ` Jan Beulich
2015-08-28 16:53 ` Lars Kurth
2015-08-31 8:23 ` [xen 4.6 retrospective] Kicking off a retrospective for Xen 4.6 (deadline August 28th) Wu, Feng
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=1439220724.24583.14.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=community.manager@xenproject.org \
--cc=lars.kurth.xen@gmail.com \
--cc=roger.pau@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.