Gluster users - Jun 2016 - 3.8 Release

Hey all, have been away for two weeks and I see there has been a 3.8 
release with some fascinating new features and a slew of fixes.


Unfortunately I'm not in a good position to pre-test before rollout now, 
we've moved all our VM's to 3.7.11 where it is working very nicely.


Is 3.8.0 considered stable for production? would I be safe to update to 
it and keep my current datastore on 3.7.11 features, but start a test 
datastore for 3.8 on the same nodes? Impossible to answer? :)


-- 
Lindsay Mathieson

<BUMP>

I am curious as well.

We are still planning an upgrade off our old 3.4 clusters which work 
perfectly fine <grin>, though they lack the sharding and thus are 
subject to the 'freeze while resync VM' problem when cluster members are
upgraded/break.

Thus we need to to know if we should be using the upcoming 3.7.12 
release or go straight to the upcoming 3.8.x branch (and avoid a rip and 
replace upgrade later on).

-wk


On 6/22/2016 4:18 PM, Lindsay Mathieson wrote:
> Hey all, have been away for two weeks and I see there has been a 3.8 
> release with some fascinating new features and a slew of fixes.
>
>
> Unfortunately I'm not in a good position to pre-test before rollout 
> now, we've moved all our VM's to 3.7.11 where it is working very
nicely.
>
>
> Is 3.8.0 considered stable for production? would I be safe to update 
> to it and keep my current datastore on 3.7.11 features, but start a 
> test datastore for 3.8 on the same nodes? Impossible to answer? :)
>
>