All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhishek Lekshmanan <abhishek@suse.com>
To: Alfredo Deza <adeza@redhat.com>, Matt Benjamin <mbenjami@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
	ceph-users <ceph-users@ceph.com>,
	"ceph-maintainers@ceph.com" <ceph-maintainers@ceph.com>,
	ceph-announce@ceph.com
Subject: Re: [ceph-users] v12.1.4 Luminous (RC) released
Date: Wed, 16 Aug 2017 15:17:04 +0200	[thread overview]
Message-ID: <8760dn4ppr.fsf@suse.com> (raw)
In-Reply-To: <CAC-Np1xzdfEVQOszKttVEx8KNEspqJ+aBdS9RRVuA--QEEd9Gg@mail.gmail.com>

Alfredo Deza <adeza@redhat.com> writes:

> On Tue, Aug 15, 2017 at 10:35 PM, Matt Benjamin <mbenjami@redhat.com> wrote:
>> I think we need a v12.1.5 including #17040
We discussed this in the RGW Standups today & may not need one more RC
for the bug above, and should be fine as far as the fix is in 12.2.0

>
> *I* think that this is getting to a point where we should just have
> nightly development releases.
>
> What is the benefit of waiting for each RC every two weeks (or so) otherwise?

We could consider something of this sort for M maybe?

Abhishek
> On one side we are treating the RC releases somewhat like normal
> releases, with proper announcements, waiting for
> QA suites to complete, and have leads "ack" when their components are
> good enough. But on the other side of things
> we then try to cut releases to include fixes as immediate as possible
> (and as often as that means)
>
> We've had 3 releases already in August and this would mean discussing
> a *fourth*. 
>
>>
>> Matt
>>
>> On Tue, Aug 15, 2017 at 5:16 PM, Gregory Farnum <gfarnum@redhat.com> wrote:
>>> On Tue, Aug 15, 2017 at 2:05 PM, Abhishek <abhishek@suse.com> wrote:
>>>> This is the fifth release candidate for Luminous, the next long term
>>>> stable release. We’ve had to do this release as there was a bug in
>>>> the previous RC, which affected upgrades to Luminous.[1]
>>>
>>> In particular, this will fix things for those of you who upgraded from
>>> Jewel or a previous RC and saw OSDs crash instantly on boot. We had an
>>> oversight in dealing with another bug. (Standard disclaimer: this was
>>> a logic error that resulted in no data changes. There were no
>>> durability implications — not that that helps much when you can't read
>>> your data out again.)
>>>
>>> Sorry guys!
>>> -Greg
>>>
>>>>
>>>> Please note that this is still a *release candidate* and
>>>> not the final release, we're expecting the final Luminous release in
>>>> a week's time, meanwhile, testing and feedback is very much welcom.
>>>>
>>>> Ceph Luminous (v12.2.0) will be the foundation for the next long-term
>>>> stable release series. There have been major changes since Kraken
>>>> (v11.2.z) and Jewel (v10.2.z), and the upgrade process is non-trivial.
>>>> Please read these release notes carefully. Full details and changelog at
>>>> http://ceph.com/releases/v12-1-4-luminous-rc-released/
>>>>
>>>> Notable Changes from 12.1.3
>>>> ---------------------------
>>>> * core: Wip 20985 divergent handling luminous (issue#20985, pr#17001, Greg
>>>> Farnum)
>>>> * qa/tasks/thrashosds-health.yaml: ignore MON_DOWN (issue#20910, pr#17003,
>>>> Sage Weil)
>>>> * crush, mon: fix weight set vs crush device classes (issue#20939, Sage
>>>> Weil)
>>>>
>>>>
>>>> Getting Ceph
>>>> ------------
>>>> * Git at git://github.com/ceph/ceph.git
>>>> * Tarball at http://download.ceph.com/tarballs/ceph-12.1.4.tar.gz
>>>> * For packages, see http://docs.ceph.com/docs/master/install/get-packages/
>>>> * For ceph-deploy, see
>>>> http://docs.ceph.com/docs/master/install/install-ceph-deploy
>>>> * Release sha1: a5f84b37668fc8e03165aaf5cbb380c78e4deba4
>>>>
>>>> [1]: http://tracker.ceph.com/issues/20985
>>>>
>>>>
>>>> Best Regards
>>>> Abhishek
>>>>
>>>> _______________________________________________
>>>> ceph-users mailing list
>>>> ceph-users@lists.ceph.com
>>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>> _______________________________________________
>>> ceph-users mailing list
>>> ceph-users@lists.ceph.com
>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>> --
>> 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
> _______________________________________________
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com


  reply	other threads:[~2017-08-16 13:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 21:05 v12.1.4 Luminous (RC) released Abhishek
2017-08-15 21:16 ` [ceph-users] " Gregory Farnum
2017-08-16  2:35   ` Matt Benjamin
     [not found]     ` <CAKOnarmpOgZL7PtHnW-xOEH589aPyNPoGkguYpWbhAgV5RcwQw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-16 12:13       ` Alfredo Deza
2017-08-16 13:17         ` Abhishek Lekshmanan [this message]
2017-08-16 15:42         ` [ceph-users] " Gregory Farnum
2017-08-16 18:26           ` Alfredo Deza
2017-08-16 23:01             ` Kamble, Nitin A
2017-08-16 23:18               ` [Ceph-maintainers] " Dan Mick
2017-08-17  1:02                 ` Kamble, Nitin A
2017-08-17  1:42                   ` Dan Mick
2017-08-17 16:18                     ` Kamble, Nitin A
2017-08-17 16:42                       ` Vasu Kulkarni
2017-08-17 16:59                         ` Kamble, Nitin A
2017-08-17 17:23                           ` Kamble, Nitin A
2017-08-17 17:37                             ` Kamble, Nitin A
2017-08-17 20:50                               ` David Zafman
2017-08-17 21:09                                 ` Kamble, Nitin A
2017-08-17 21:21                                   ` David Zafman
2017-08-17 21:27                                     ` Kamble, Nitin A
2017-08-23 19:15                                   ` Sage Weil
2017-08-23 21:20                                     ` Kamble, Nitin A
2017-08-23 21:33                                       ` Sage Weil
2017-08-24  1:26                                         ` Kamble, Nitin A
2017-08-24  2:19                                           ` Sage Weil
2017-08-24  2:49                                             ` Sage Weil
2017-08-24 16:33                                             ` Kamble, Nitin A
2017-08-24 19:58                                               ` Sage Weil
2017-08-24 21:34                                                 ` Kamble, Nitin A
2017-08-25 22:11                                                   ` Sage Weil
2017-08-25 22:17                                                     ` Kamble, Nitin A
2017-08-25 22:27                                                       ` Kamble, Nitin A
2017-08-17  7:45                   ` Henrik Korkuc
2017-08-18 17:39         ` Nathan Cutler
2017-08-21 12:14           ` Alfredo Deza

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=8760dn4ppr.fsf@suse.com \
    --to=abhishek@suse.com \
    --cc=adeza@redhat.com \
    --cc=ceph-announce@ceph.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-maintainers@ceph.com \
    --cc=ceph-users@ceph.com \
    --cc=mbenjami@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.