On Tue, May 21, 2013 at 7:49 PM, Joe Brockmeier wrote:
> Hi all,
>
> We apparently have a regression in 4.0.2 that will break new deployments
> on Ceph RDB, and I was also CC'ed on another fix last week that could
> apply to the 4.0.x branch.
>
> The thought was that we would not have another rel
On Wed, May 22, 2013, at 09:26 AM, Wido den Hollander wrote:
> On 05/21/2013 10:03 PM, Chip Childers wrote:
> The longer I think about it, the more I agree. Since these issues have
> been resolved in 4.1 and we are so close, we'd better focus on 4.1
> indeed.
>
> Since I think 4.0.3 would only be
On 05/21/2013 10:03 PM, Chip Childers wrote:
On Tue, May 21, 2013 at 10:21:14AM -0400, Chip Childers wrote:
On Tue, May 21, 2013 at 09:19:05AM -0500, Joe Brockmeier wrote:
Hi all,
We apparently have a regression in 4.0.2 that will break new deployments
on Ceph RDB, and I was also CC'ed on anot
On Tue, May 21, 2013 at 10:21:14AM -0400, Chip Childers wrote:
> On Tue, May 21, 2013 at 09:19:05AM -0500, Joe Brockmeier wrote:
> > Hi all,
> >
> > We apparently have a regression in 4.0.2 that will break new deployments
> > on Ceph RDB, and I was also CC'ed on another fix last week that could
>
On Tue, May 21, 2013 at 09:19:05AM -0500, Joe Brockmeier wrote:
> Hi all,
>
> We apparently have a regression in 4.0.2 that will break new deployments
> on Ceph RDB, and I was also CC'ed on another fix last week that could
> apply to the 4.0.x branch.
>
> The thought was that we would not have a
Hi all,
We apparently have a regression in 4.0.2 that will break new deployments
on Ceph RDB, and I was also CC'ed on another fix last week that could
apply to the 4.0.x branch.
The thought was that we would not have another release in the 4.0.x
branch because we're so close to 4.1.0, but right
