kraken rc is out, and kraken is branched!

kraken rc is out, and kraken is branched!

[Sage Weil]

Please continue to target PRs at master; we will cherry-pick -x them to 
kraken.  This isn't quite what we usually do (if there is a "usually" 
here), but for RBD we are reverting some half-completed features and we 
don't want those to get merged back into master.

Thanks!
sage

Re: kraken rc is out, and kraken is branched!

[Zhi Zhang]

Hi Sage, or others,

Just a quick question. Which ceph version will be the next long term
support after Hammer? Jewel or Kraken or both?

We are using Hammer on production, but still met some bugs which have
been fixed in higher ceph version. And some of the bug fixes are
really not easy to backport because of the code base those fixes
depend on, so we have to fix them or workaround them in our internal
code base. We would like to try avoiding such things later after we
choose a higher version to upgrade. So want to ask for some
suggestions here with stability, compatibility and long-term
supporting into consideration.

Thanks a lot.

Regards,
Zhi Zhang (David)
Contact: zhang.david2011@gmail.com
              zhangz.david@outlook.com


On Wed, Dec 14, 2016 at 7:51 AM, Sage Weil <sweil@redhat.com> wrote:
> Please continue to target PRs at master; we will cherry-pick -x them to
> kraken.  This isn't quite what we usually do (if there is a "usually"
> here), but for RBD we are reverting some half-completed features and we
> don't want those to get merged back into master.
>
> Thanks!
> sage
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: kraken rc is out, and kraken is branched!

[Sage Weil]

On Wed, 14 Dec 2016, Zhi Zhang wrote:
> Hi Sage, or others,
> 
> Just a quick question. Which ceph version will be the next long term
> support after Hammer? Jewel or Kraken or both?

Jewel.  The next LTS after that will be Luminous, which is due out in the 
spring.

You can find this information here:

	http://docs.ceph.com/docs/master/releases/

sage

> We are using Hammer on production, but still met some bugs which have
> been fixed in higher ceph version. And some of the bug fixes are
> really not easy to backport because of the code base those fixes
> depend on, so we have to fix them or workaround them in our internal
> code base. We would like to try avoiding such things later after we
> choose a higher version to upgrade. So want to ask for some
> suggestions here with stability, compatibility and long-term
> supporting into consideration.
> 
> Thanks a lot.
> 
> Regards,
> Zhi Zhang (David)
> Contact: zhang.david2011@gmail.com
>               zhangz.david@outlook.com
> 
> 
> On Wed, Dec 14, 2016 at 7:51 AM, Sage Weil <sweil@redhat.com> wrote:
> > Please continue to target PRs at master; we will cherry-pick -x them to
> > kraken.  This isn't quite what we usually do (if there is a "usually"
> > here), but for RBD we are reverting some half-completed features and we
> > don't want those to get merged back into master.
> >
> > Thanks!
> > sage
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
>