All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Bonvalet <ceph.list@daevel.fr>
To: Yuri Weinstein <yweinste@redhat.com>,
	Ceph Development <ceph-devel@vger.kernel.org>
Cc: Loic Dachary <ldachary@redhat.com>,
	Xinxin Shu <xinxin.shu@intel.com>,
	Alfredo Deza <adeza@redhat.com>, Sage Weil <sweil@redhat.com>
Subject: Re: firefly v0.80.10 QE validation completed
Date: Mon, 22 Jun 2015 09:40:20 +0200	[thread overview]
Message-ID: <1434958820.2806.3.camel@daevel.fr> (raw)
In-Reply-To: <628525610.25137687.1434591207216.JavaMail.zimbra@redhat.com>

Hi,

I saw the proposed upgrade to 0.80.10 this morning, but can't find the
announce about this (neither by email or on the website).

Is the 0.80.10 ready to be used ?

thanks,
Olivier

Le mercredi 17 juin 2015 à 21:33 -0400, Yuri Weinstein a écrit :
> firefly v0.80.10 is ready for publishing (Sage, Alfredo, Loic, Xinxin 
> FYI)
> 
> All results details were summarized in 
> http://tracker.ceph.com/issues/11090
> 
> Note:
> 
> - upgrade/dumpling-firefly-x (to hammer)(distros) - runs out of 
> memory on vps and unreliable
> - #11957 fixed (thanks Ilya, Zack!) and tested
> 
> Thx
> YuriW
> 
> ----- Original Message -----
> From: "Yuri Weinstein" <yweinste@redhat.com>
> To: "Ceph Development" <ceph-devel@vger.kernel.org>
> Cc: "Loic Dachary" <ldachary@redhat.com>, "Xinxin Shu" <
> xinxin.shu@intel.com>
> Sent: Monday, June 15, 2015 9:37:20 AM
> Subject: firefly v0.80.10 QE validation status 6/15/2015
> 
> QE validation is almost completed (there are a couple of jobs that 
> are still running)
> 
> All statis details were summarized in 
> http://tracker.ceph.com/issues/11090
> 
> Highlights (by suite/issue):
> 
> rados #11914 needs Sam's approval
> kcephfs n/a needs Greg's approval
> samba #6613 needs Greg's approval
> 
> Nice to have fixes (no blockers):
> upgrade/firefly(distros) #11957	(env noise)
> 
> 
> Thx
> YuriW
> --
> 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
> --
> 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
> 
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in

  parent reply	other threads:[~2015-06-22  7:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <515457523.22063779.1434385426136.JavaMail.zimbra@redhat.com>
2015-06-15 16:37 ` firefly v0.80.10 QE validation status 6/15/2015 Yuri Weinstein
2015-06-15 17:19   ` Samuel Just
2015-06-16 10:02   ` Gregory Farnum
2015-06-18  1:33   ` firefly v0.80.10 QE validation completed Yuri Weinstein
2015-06-18  3:13     ` VPS memory Sage Weil
2015-06-18  4:49       ` Yuri Weinstein
2015-06-18 20:43       ` Tamil Muthamizhan
2015-06-22  7:40     ` Olivier Bonvalet [this message]
2015-06-22  8:48       ` firefly v0.80.10 QE validation completed Loic Dachary
2015-06-22  8:52         ` Dan van der Ster
2015-06-22  9:12           ` Loic Dachary

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=1434958820.2806.3.camel@daevel.fr \
    --to=ceph.list@daevel.fr \
    --cc=adeza@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ldachary@redhat.com \
    --cc=sweil@redhat.com \
    --cc=xinxin.shu@intel.com \
    --cc=yweinste@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.