Am 05.06.2012 15:43, schrieb Louis Zuckerman:
Hi Patrick,
I have updates to the debian packaging for Glusterfs 3.3.0 that I am
ready to commit. Can we get 3.3.0 into wheezy? Or should I wait to
contribute the 3.3.0 updates until you have a 3.2.7 build in testing?
I just wanted to upload 3.3.0 to experimental after 3.2.7 is uploaded to
testing/unstable. Just commit, I will create the branch for wheezy then.
In my opinion we should move forward with 3.3.0 since it is available
now and includes many improvements over the 3.2 branch.
Since Wheezy freezes this month it would be safer to use a longer tested
version for a stable release. glusterfs 3.3.0 has got interesting new
features, but it may be too new :( Just a bad timing
Please advise.
Thanks!
-louis
On Mon, Jun 4, 2012 at 2:11 PM, Vijay Bellur<vbellur@xxxxxxxxxx> wrote:
On 06/04/2012 10:34 PM, Patrick Matthäi wrote:
Am 25.05.2012 20:56, schrieb Patrick Matthäi:
Am 12.04.2012 19:29, schrieb Vijay Bellur:
http://bits.gluster.com/pub/gluster/glusterfs/3.2.7qa1/
http://bits.gluster.com/pub/gluster/glusterfs/src/glusterfs-3.2.7qa1.tar.gz
This release is made off v3.2.7qa1
Hey,
I have tested this qa release and could not find any regression/problem.
It would be realy nice to have a 3.2.7 release in the next days (max 2
weeks from now on) so that we could ship glusterfs 3.2.7 instead of
3.2.6 with our next release Debian Wheezy!
Didn't get an answer yet, is there any release schedule?
Sorry, I missed this. We can release 3.2.7 in a week from now. Would that
work for inclusion in Debian Wheezy?
Thanks,
Vijay
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
https://lists.nongnu.org/mailman/listinfo/gluster-devel
