On Tue, May 21, 2013 at 04:15:20PM +0200, Wido den Hollander wrote:
> I didn't know we weren't going to release 4.0.3.
We've discussed the support lifetime on and off for awhile now.
Consensus seemed to be that we would support each minor version release
(the feature releases like 4.1 and 4.2) unt
On 05/21/2013 04:08 PM, Chip Childers wrote:
On Tue, May 21, 2013 at 04:06:18PM +0200, Wido den Hollander wrote:
Hi,
I just came into contact with a user on IRC who was running into
problems with 4.0.2 due to this RBD bug.
Can we cherry-pick this back to 4.0 and release 4.0.3?
There wasn't a
On Tue, May 21, 2013, at 09:08 AM, Chip Childers wrote:
> There wasn't a plan to do a 4.0.3, but I guess you could run with it if
> you wanted to push that out there. Alternatively, help getting 4.1.0
> out the door (with this fix) could be another path to helping that user.
I'm planning to be of
On Tue, May 21, 2013 at 04:06:18PM +0200, Wido den Hollander wrote:
> Hi,
>
> I just came into contact with a user on IRC who was running into
> problems with 4.0.2 due to this RBD bug.
>
> Can we cherry-pick this back to 4.0 and release 4.0.3?
There wasn't a plan to do a 4.0.3, but I guess you
Hi,
I just came into contact with a user on IRC who was running into
problems with 4.0.2 due to this RBD bug.
Can we cherry-pick this back to 4.0 and release 4.0.3?
It's currently breaking all setups who are using RBD or want to start
deploying with RBD.
Wido
On 05/17/2013 10:21 AM, Wido
