From: James Page <james.page@ubuntu.com>
To: Sage Weil <sage@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: firefly timing
Date: Tue, 04 Feb 2014 08:14:13 +0200 [thread overview]
Message-ID: <52F08535.50100@ubuntu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1402030819030.6345@cobra.newdream.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 03/02/14 18:21, Sage Weil wrote:
> The only time dependency that I am aware of is the looming 14.04
> freeze date. I'm hoping that we can (worst case) put an -rc
> release in place and update as the code stabilizes over the next
> several weeks. James, will this be problematic?
Pushing in an RC is a good approach; what's the likely date for the
firefly release? I can raise the Freeze Exception now which gives our
release team *lots* of notice :-) FWIW I don't think this will be a
problem - we have a good track record with ceph in Ubuntu now.
Cheers
James
- --
James Page
Ubuntu and Debian Developer
james.page@ubuntu.com
jamespage@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJS8IU1AAoJEL/srsug59jDEQkP/Ak1DvMqDsLwtdWNJCZ6Y4qM
/+GhBuJHCEDhx7+2mM4l9kiFdEVRNY4uarRIaCNYtgMhKWZ0c1MzFD4nVicqmg85
72gfdc97opDU3Mus3GXk6TI51jex6YBaRR4kUDWcT5l2N39yPN9iaxiSftfYnI4C
3sK5W2GdLCaYjWsjgdOum0UDyN9ZSZmK1qBfMHmZZ74OsMPmGK+D9hiTKnH5sEF8
57Nmoa4G4wfmBUf/vxkKnmI51hQrXnp0zqeI5i+xDvDGelNUDtofrcxQrp0yfnff
FAf50KvYeniyjvtgqQMvu9vrb4gvN0lTFUZygLXICq5mX45JitGjQ0NS7T4pVhbE
fdW+2BN4I91CkIVY/qPTRqWv/RIZJM4dj/2w3DBMhoMnIl1laFd+uMd5b2mxrWD9
RHXOOXgE9fq0gBuB5N2w8Q50Bm4+gDqxM7mfQi8lvSjXyUVPdvdnIuYd/L5beIGX
9EbYLLoaXRHIN84DQwHY/6Ni57rPGcG0VNjOBcgNXr/8DXJi4b8ztxIpCT7rhpG0
UeCVEuRsrM5wggvQFODaxQ1BzNvuQbUryj+FK2fsGfwnHESp1J5arKbRJUUHCkT7
tzhHlqx9jWDp6sMyc6jMVotSOgQv/AGq+kt/gBLEz6ymLB4MsZkQQRpMXXID+RkH
tmFj4DUwOn7LRSS1/Ag8
=kovj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-02-04 6:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 16:21 firefly timing Sage Weil
2014-02-03 17:29 ` Loic Dachary
2014-02-04 6:14 ` James Page [this message]
2014-02-04 6:20 ` Sage Weil
2014-02-04 6:33 ` James Page
-- strict thread matches above, loose matches on Subject: below --
2014-03-18 4:45 Sage Weil
[not found] ` <alpine.DEB.2.00.1403172115140.24236-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18 7:07 ` Stefan Priebe - Profihost AG
[not found] ` <5327F0A7.8010105-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2014-03-18 7:13 ` Ирек Фасихов
[not found] ` <CAF-rypyVjvuddtaj=cW_yJowzGzCq0m7LgW6S=2zK1aAvsfrTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-18 7:54 ` Karan Singh
2014-03-18 10:00 ` Alexandre DERUMIER
2014-03-18 16:06 ` Sage Weil
[not found] ` <alpine.DEB.2.00.1403180905500.316-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18 16:20 ` Stefan Priebe - Profihost AG
2014-03-18 16:38 ` Milosz Tanski
[not found] ` <CANP1eJEDccw7doegUSoNKceQUgoNOfpHW1_y1Oz1fk54WDdb4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-18 17:17 ` Sage Weil
[not found] ` <alpine.DEB.2.00.1403181014410.5823-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18 20:12 ` Sage Weil
2014-03-18 22:32 ` Milosz Tanski
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=52F08535.50100@ubuntu.com \
--to=james.page@ubuntu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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.