Bernard, I would suggest that you go ahead and commit the patches that you described below, to trunk. If it turns out that there are any comments that would cause them to change, we can deal with it in SVN and just commit new patches. This will avoid having to make everybody do manual patching to try out the new code. From my perspective, trunk is for reasonable innovation (ie. commit innovative patches to the existing code. Don't commit a complete rewrite of the code without first checking the list). We can always back anything out of trunk that we don't think is good idea. In the Apache project, this is called Commit-Then-Review (CTR). Patches are commited to trunk at anytime and then reviewed by the community. There is a different model used in the stable branch (in our case the 3.0.x branch). That model is Review-Then-Commit (RTC). Since we want to make sure that the stable branch remains stable, patches must be reviewed on the list before being committed to the branch.
Release procedures is another topic we can discuss at the meeting if we find it necessary. Brad >>> On 2/8/2008 at 6:12 PM, in message <[EMAIL PROTECTED]>, "Bernard Li" <[EMAIL PROTECTED]> wrote: > Hi guys: > > The latest snapshot of Ganglia trunk (3.1.x) based on r942 is now available: > > http://www.ganglia.info/snapshots/3.1.x > > This includes the latest code patches I have submitted to this list > but haven't been committed yet, this includes: > > 1) Group host metric graphs by EXTRA_DATA GROUP > 2) Use EXTRA_DATA TITLE as the title of host metric graphs > 3) Use EXTRA_DATA DESC as <img title> tag for "cheap" tooltip on hover > over metric graphs > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
