Based on my experiences so far, I would absolutely agree with you. I know new releases are hard to produce at 100% coming out of the gate, so the fact that 3.2 is not all that robust is unsurprising to me. Hopefully the point releases improve this. I would really like to see the known bugs in 3.1.4 fixed in a later point release in that branch. I do agree slightly with Stephan (which is unusual) that features over stability seems to be the current direction for the project. The shame of that is that stability has got to be the #1 priority for any features to be useful. That said, 3.1.3 does seem pretty solid to me now, compared with 3.1.1 and with 3.0.4. I disagree with Stephan about everything after 2.0.9 being "bogus". Just because the development direction does not correspond with a single individuals needs doesn't mean it's worthless or "totally broken" for others. The additional features for non-downtime changes to the storage nodes are very useful to us here - though more robust behavior and better documentation would be welcome. Just my two cents -----Original Message----- From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Whit Blauvelt Sent: Wednesday, May 18, 2011 9:55 AM To: Udo Waechter Cc: gluster-users at gluster.org Subject: Re: gluster 3.2.0 - totally broken?
