All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhishek Lekshmanan <abhishek-IBi9RG/b67k@public.gmane.org>
To: Paul Emmerich <paul.emmerich-iZXOWb+A65A@public.gmane.org>
Cc: ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	ceph-users <ceph-users-Qp0mS5GaXlQ@public.gmane.org>
Subject: Re: v12.2.12 Luminous released
Date: Mon, 15 Apr 2019 12:58:37 +0200	[thread overview]
Message-ID: <87r2a3tu02.fsf@suse.com> (raw)
In-Reply-To: <CAD9yTbFKWkxy5JRo0H8jF6_agCB=tfeHXi87YCPC+UkX-O1GsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Paul Emmerich <paul.emmerich@croit.io> writes:

> I think the most notable change here is the backport of the new bitmap
> allocator, but that's missing completely from the change log.

Updated the changelog in docs and the blog. The earlier script was
ignoring entries that didn't link to backport tracker following back to
a master tracker.
>
>
> Paul
>
> -- 
> Paul Emmerich
>
> Looking for help with your Ceph cluster? Contact us at https://croit.io
>
> croit GmbH
> Freseniusstr. 31h
> 81247 München
> www.croit.io
> Tel: +49 89 1896585 90
>
> On Fri, Apr 12, 2019 at 6:48 PM Abhishek Lekshmanan <abhishek@suse.com> wrote:
>>
>>
>> We are happy to announce the next bugfix release for v12.2.x Luminous
>> stable release series. We recommend all luminous users to upgrade to
>> this release. Many thanks to everyone who contributed backports and a
>> special mention to Yuri for the QE efforts put in to this release.
>>
>> Notable Changes
>> ---------------
>> * In 12.2.11 and earlier releases, keyring caps were not checked for validity,
>>   so the caps string could be anything. As of 12.2.12, caps strings are
>>   validated and providing a keyring with an invalid caps string to, e.g.,
>>   `ceph auth add` will result in an error.
>>
>> For the complete changelog, please refer to the release blog entry at
>> https://ceph.com/releases/v12-2-12-luminous-released/
>>
>> Getting ceph:
>> ------------
>> * Git at git://github.com/ceph/ceph.git
>> * Tarball at http://download.ceph.com/tarballs/ceph-12.2.12.tar.gz
>> * For packages, see http://docs.ceph.com/docs/master/install/get-packages/
>> * Release git sha1: 1436006594665279fe734b4c15d7e08c13ebd777
>>
>> --
>> Abhishek Lekshmanan
>> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>> HRB 21284 (AG Nürnberg)
>

-- 
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

  parent reply	other threads:[~2019-04-15 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 16:48 v12.2.12 Luminous released Abhishek Lekshmanan
     [not found] ` <87tvf3tbik.fsf-IBi9RG/b67k@public.gmane.org>
2019-04-13  0:03   ` Paul Emmerich
     [not found]     ` <CAD9yTbFKWkxy5JRo0H8jF6_agCB=tfeHXi87YCPC+UkX-O1GsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-04-15 10:58       ` Abhishek Lekshmanan [this message]
     [not found]         ` <87r2a3tu02.fsf-IBi9RG/b67k@public.gmane.org>
2019-04-15 14:26           ` Paul Emmerich

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=87r2a3tu02.fsf@suse.com \
    --to=abhishek-ibi9rg/b67k@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    --cc=paul.emmerich-iZXOWb+A65A@public.gmane.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.