All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	zhenzhong.duan@oracle.com
Subject: Re: Xen 4.4 development update: Code freezing point reached
Date: Tue, 19 Nov 2013 10:11:36 -0500	[thread overview]
Message-ID: <20131119151136.GB5790@phenom.dumpdata.com> (raw)
In-Reply-To: <528B89AB0200007800104900@nat28.tlf.novell.com>

On Tue, Nov 19, 2013 at 02:54:19PM +0000, Jan Beulich wrote:
> >>> On 19.11.13 at 15:40, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > On Mon, Nov 18, 2013 at 06:19:46PM +0000, George Dunlap wrote:
> >> The idea is that today we will be pretty permissive, but that we will
> >> become progressively more conservative until the first RC, which is
> >> scheduled for 3 weeks' time (6 December).  After that, we will only
> >> accept bug fixes.
> >> 
> >> Bug fixes can be checked in without a freeze exception throughout the
> >> code freeze, unless the maintianer thinks they are particularly high
> >> risk.  In later RC's, we may even begin rejecting bug fixes if the
> >> broken functionality is small and the risk to other functionality is
> >> high.
> >> 
> >> Features which are currently marked "experimental" or do not at the
> >> moment work at all cannot be broken really; so changes to code only
> >> used by those features should be able to get a freeze exception
> >> easily.  (Tianocore is something which would probably fall under
> >> this.)
> >> 
> >> Features which change or add new interfaces which will need to be
> >> supported in a backwards-compatible way (for instance, vNUMA) will
> >> need freeze exceptions to make sure that the interface itself has
> >> enough time to be considered stable.
> >> 
> >> These are guidelines and principles to give you an idea where we're
> >> coming from; if you think there's a good reason why making an
> >> exception for you will help us achieve goals 1-3 above better than not
> >> doing so, feel free to make your case.
> > 
> > I am wondering in which category the tmem cleanup patches fall?
> > 
> > They aren't bug-fixes, they could be considered a feature. They were
> > posted before the deadline. I posted the GIT PULL (see
> > http://article.gmane.org/gmane.comp.emulators.xen.devel/178043)
> > to one of the folks who has write access to the repository (as
> > documented in http://www.xenproject.org/governance.html)? 
> 
> Considering the state of TMEM, I think these could go in at almost
> any time. (Btw, I would have committed them already, but wasn't
> up to trying out my first git pull from a foreign tree, due to my
> expectation of it not going to work as I expect the first time

:-)
> through, and there's other more important work that needs my
> attention first. And of course you sent the pull request to Keir
> only anyway...)

Duh! I will make sure to send it all committers in the hypervisor
next time.

Thanks!

  reply	other threads:[~2013-11-19 15:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 18:19 Xen 4.4 development update: Code freezing point reached George Dunlap
2013-11-18 18:52 ` Dario Faggioli
2013-11-18 19:22 ` Pasi Kärkkäinen
2013-11-19 16:18   ` George Dunlap
2013-11-19  0:59 ` Don Slutz
2013-11-19 17:46   ` George Dunlap
2013-11-19 10:50 ` Roger Pau Monné
2013-11-19 11:06   ` George Dunlap
2013-11-19 11:31     ` Roger Pau Monné
2013-11-19 14:00 ` Ian Campbell
2013-11-19 14:40 ` Konrad Rzeszutek Wilk
2013-11-19 14:54   ` Jan Beulich
2013-11-19 15:11     ` Konrad Rzeszutek Wilk [this message]
2013-11-19 17:52   ` George Dunlap
2013-11-19 19:40     ` Konrad Rzeszutek Wilk
2013-11-20  3:17   ` Zhenzhong Duan

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=20131119151136.GB5790@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=zhenzhong.duan@oracle.com \
    /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.