From: Abhishek Lekshmanan <abhishek@suse.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Cc: Gregory Farnum <greg@gregs42.com>, Samuel Just <sjust@redhat.com>,
Yehuda Sadeh-Weinraub <yehuda@redhat.com>,
Jason Dillaman <jdillama@redhat.com>
Subject: Heads up for releasing the next kraken dev release
Date: Fri, 07 Oct 2016 00:16:53 +0200 [thread overview]
Message-ID: <87d1jdt962.fsf@suse.com> (raw)
We're in position to cut the next development release of kraken, 11.0.1,
barring no blockers from the leads we'll be cutting the next dev. release soonish.
Best,
Abhishek
reply other threads:[~2016-10-06 22:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87d1jdt962.fsf@suse.com \
--to=abhishek@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@gregs42.com \
--cc=jdillama@redhat.com \
--cc=sjust@redhat.com \
--cc=yehuda@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.