Re: [Ganglia-developers] 3.0.x release, make 3.1 maintenance branch, create 3.2 release branch

[Bernard Li <be...@va...>]

Hi Carlo:

On Fri, Oct 8, 2010 at 12:31 AM, Carlo Marcelo Arenas Belon
<ca...@sa...> wrote:

> mostly everyone using EPEL packages in CentOS/RHEL is using 3.0 and
> so EOL than branch (like was done for 2.5 which was until recently
> all that was provided by debian and still what is distributed in
> by Novell) would be IMHO a bad idea.

I can see your point but if nobody is going to maintain that branch
then the point is moot.  I'd much rather we make one final release and
move on.

As far as EPEL is concerned, Kostas is going to work on a ganglia31
package that will bring EL5 up to 3.1 but for EL4 it's tricky since it
does not provide apr1 so it will likely stay on 3.0.x.  For EL4 users
who would like to upgrade to 3.1.x, they can still do so by installing
apr1 in parallel to apr0, but they would have to track security
updates separately.

> if all you want is to have a 3.2 release branch (what would be the
> main feature on it, though?) then just do so; why affect 3.0 or 3.1
> but that decision?

At any given point in time, we have three ongoing branches:
development (trunk), release (3.1) and maintenance (3.0).  If we are
to create a 3.2 branch, then something has to give.  I don't think we
have enough manpower to maintain more then 3 simultaneous branches.

As for new features, the sFlow work which Brad mentioned, the numerous
frontend enhancements like Ramon's graph statistics, Timothy's custom
time calendar, Jamie's recent patch for specific host/cluster/grid
custom graphs, gmetad-python by Matt Ryan and Brad are all good
candidates for 3.2 release.

Cheers,

Bernard