Re: [Gluster-users] [Gluster-devel] GlusterFS-1.4 to become GlusterFS-2.0

2009-01-14 Thread Kevan Benson
Sean Davis wrote: On Mon, Jan 5, 2009 at 4:09 PM, Kevan Benson kben...@a-1networks.comwrote: Anand Babu Periasamy wrote: 2.0.0rc1 will be available in a week. Before we call it 2.0.0, we want to to achieve the following: * Binary packages for GNU/Linux (rpm/deb), FreeBSD, Mac OS X and Solaris

Re: [Gluster-users] [Gluster-devel] GlusterFS-1.4 to become GlusterFS-2.0

2009-01-14 Thread Dan Parsons
In my install of 1.4rc7, /sbin/mount.glusterfs is a simple shell script, and glusterfs is actually a symlink to glusterfsd. So, in short, I'd have to say that in 1.4rc7, yes, the client and server are one binary. Dan Parsons On Jan 14, 2009, at 12:38 PM, Kevan Benson wrote: Sean Davis

Re: [Gluster-users] [Gluster-devel] GlusterFS-1.4 to become GlusterFS-2.0

2009-01-14 Thread Kevan Benson
Dan Parsons wrote: In my install of 1.4rc7, /sbin/mount.glusterfs is a simple shell script, and glusterfs is actually a symlink to glusterfsd. So, in short, I'd have to say that in 1.4rc7, yes, the client and server are one binary. Oh, well mark that down to me not showing due diligence.

Re: [Gluster-devel] GlusterFS-1.4 to become GlusterFS-2.0

2009-01-05 Thread Dan Parsons
I'm about to switch from 1.3.11 to the latest rc of 1.4... how much different will 2.0 be from 1.4? Or will 2.0 effectively be the latest version of 1.4 rc7 + bug fixes etc? Or will it be a totally different branch? I suppose the best course of action would be to wait until 2.0 but I

Re: [Gluster-devel] GlusterFS-1.4 to become GlusterFS-2.0

2009-01-05 Thread Amar Tumballi (bulde)
I'm about to switch from 1.3.11 to the latest rc of 1.4... how much different will 2.0 be from 1.4? Or will 2.0 effectively be the latest version of 1.4 rc7 + bug fixes etc? Or will it be a totally different branch? It will be 1.4 rc7 + bug fixes.

[Gluster-devel] GlusterFS-1.4 to become GlusterFS-2.0

2009-01-05 Thread Anand Babu Periasamy
Dear Community, Since the 1.3 release, we have come a long way to reach this level of code maturity. We are preparing to call the next release as the 2.0.0 instead of 1.4.0. There are real technical reasons to do so. We want to sincerely apologize for this confusion. REASONS FOR THE VERSION