All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <jdurgin@redhat.com>
To: Sage Weil <sweil@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: infernalis feature freeze
Date: Thu, 13 Aug 2015 14:26:36 -0700	[thread overview]
Message-ID: <55CD0B8C.6090907@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1508121411400.22099@cobra.newdream.net>

It'd be nice to get omap in the python bindings, it's been a pain not
having it several times:

https://github.com/ceph/ceph/pull/5272

On 08/12/2015 02:20 PM, Sage Weil wrote:
> The infernalis feature freeze is coming up Real Soon Now.  I've marked
> some of the pull requests on github that I would like to see merged.
> Please take a look:
>
> 	https://github.com/ceph/ceph/pulls?q=is%3Aopen+is%3Apr+milestone%3Ainfernalis
>
> Ideally we should focus our testing efforts on whatever is on this list.
>
> I didn't look at the bug fix PRs carefully since generally these go in
> once tested regardless of any feature freeze, but I suggest we mark things
> that need to make it into infernalis anyway so that we focus our efforts.
>
> The big items on my list that are pending testing are:
>
> 	wip-newstore-sort (teuthology running now)
> 	wip-newstore (will be marked experimental)
> 	wip-osd-compat (enforces upgrades include hammer, needs qa)
> 	wip-user (run daemons as user 'ceph')
> 	proxy writes (Sam is testing this)
> 	bufferlist tuning (performance)
> 	MOSDOp staged decoding (performance)
>
> There's tons of other stuff pending that is not on this list.  As always,
> our ability to merge code is limited primarily on our ability to test
> it--we can't afford to destabilize core ceph by merging something that we
> aren't confident will work correctly and will not easily break down the
> line.  If you have something pending that you want to get in, the single
> biggest thing you can do to help that happen is to write more or better
> tests for it (e.g., things that run during 'make check') and to run the
> teuthology regression suite (see Loic's recent blogs about doing this with
> OpenStack[1]).
>
> Thanks!
> sage
>
> [1] http://dachary.org/?p=3852


  parent reply	other threads:[~2015-08-13 21:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 21:20 infernalis feature freeze Sage Weil
2015-08-13  2:29 ` Haomai Wang
2015-08-13  2:46 ` Li Wang
2015-08-13 21:26 ` Josh Durgin [this message]
2015-08-18 22:52 ` Robin H. Johnson
2015-08-25 16:54   ` Yehuda Sadeh-Weinraub
2015-08-25 19:51     ` Robin H. Johnson

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=55CD0B8C.6090907@redhat.com \
    --to=jdurgin@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sweil@redhat.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.