Re: [Ganglia-developers] Ganglia 3.1 status?

2008-06-30 Thread Bernard Li
Hi Daniel:

On Mon, Jun 30, 2008 at 6:59 AM,  [EMAIL PROTECTED] wrote:

First of all, thanks for your interest in testing 3.1 and contributing
to the project.

 Is anyone using the Ganglia 3.1 code right now and able to share any
 comments about it?

 Is there anything really broken in the current code?

I am using it in a test environment with no major issue.

I have posted an email comparing the metric sizes between 3.0.x and
3.1.x, you might want to have a look:

http://www.mail-archive.com/ganglia-developers@lists.sourceforge.net/msg04204.html

Otherwise, I think 3.1.x is fairly stable but we could still use more
tests especially scalability (i.e. running the code on large number of
hosts).

 I am planning some development activity involving Ganglia and the 3.1
 module interface seems really relevant, it is likely that we will start
 writing code to take advantage of this API.

Cool.

 Which branch should I take from the repository: trunk or
 branches/monitor-core-3.1 ?

Trunk is 3.2.x, so you would want to work with branches/monitor-core-3.1.

 If I want to contribute any bug fixes or enhancements to the project,
 should I be working on trunk or start my own branch?

Enhancements definitely should go to trunk.

monitor-core-3.1 is considered a stable branch now, so if there are
bugfixes, they need to be fixed in trunk and then proposed to be
included for 3.1.x branch.

Either way, submit patches via bugzilla.ganglia.info and we'll take it
from there.

Cheers,

Bernard

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] Ganglia 3.1 status?

2008-06-30 Thread Carlo Marcelo Arenas Belon
On Mon, Jun 30, 2008 at 02:59:20PM +0100, [EMAIL PROTECTED] wrote:
 
 Is there anything really broken in the current code?

hope not, even if there are some minor issues that are most likely irrelevant
if you are planning to work in some well supported architecture or find the
current snapshots suitable.

 I am planning some development activity involving Ganglia and the 3.1
 module interface seems really relevant, it is likely that we will start
 writing code to take advantage of this API.

what is that you are planning to work in?

 Which branch should I take from the repository: trunk or
 branches/monitor-core-3.1 ?
 
 If I want to contribute any bug fixes or enhancements to the project,
 should I be working on trunk or start my own branch?

trunk is where all development is done, for an explanation take a look at :

  http://ganglia.wiki.sourceforge.net/ganglia_works

and other related documents in the wiki; once the code is integrated there and
stabilized it will be backported into 3.1 if relevant.

if what you are planning is big enough I'll recommend creating a local branch
using git svn so that it will be easy for you to maintain your patches out
of tree, without having to block your development while they get integrated
and without having to resort to huge patches with unrelated changes.

Carlo

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] Ganglia 3.1 status?

2008-06-30 Thread Witham, Timothy D
Either way, submit patches via bugzilla.ganglia.info and we'll take it
from there.

When do bugzilla patches get considered for inclusion in trunk or
stable?  It seems like the longer you wait the harder it is to apply the
patches.  I always use patches from bz#38, 92, 176, 184 and 186:

http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=38
http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=92
http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=176
http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=184
http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=186

-twitham

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers


Re: [Ganglia-developers] Ganglia 3.1 status?

2008-06-30 Thread Bernard Li
Hi Timothy:

On Mon, Jun 30, 2008 at 12:26 PM, Witham, Timothy D
[EMAIL PROTECTED] wrote:

 When do bugzilla patches get considered for inclusion in trunk or
 stable?  It seems like the longer you wait the harder it is to apply the
 patches.  I always use patches from bz#38, 92, 176, 184 and 186:

Well, as you know we have a limited number of developers and as the
release draws near, we're all busy trying to get it out the door.

Anyhow, we encourage other users to provide comments and/or review
patches in bugzilla which would then help us with the review process.

 http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=176

The idea is great, but I think we should make the formatting/layout a
bit better such that it fits in more with the original frontend look 
view.  I'll see if I have some time to work on this.

 http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=184

I will take a look at this next.

 http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=186

I added a comment to this already -- should be able to be checked into trunk.

Cheers,

Bernard

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers