I've just added a backport proposal in the monitor-core-3.1 branch STATUS file for including a check for the module magic number. Please check out the proposal in the STATUS file and vote. You don't necessarily have to vote within the STATUS file itself, but you can or you can just vote through the devel list.
Brad >>> On 4/18/2008 at 1:12 PM, in message <[EMAIL PROTECTED]>, "Brad Nicholes" <[EMAIL PROTECTED]> wrote: >>>> On 4/18/2008 at 3:28 AM, in message <[EMAIL PROTECTED]>, Carlo > Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote: >> On Thu, Apr 17, 2008 at 03:42:05PM -0600, Brad Nicholes wrote: >>> Bernard, >>> Are we ready to produce a beta from the 3.1 branch? >> >> I though we agreed we will be releasing an alpha as soon as the following is >> completed : >> >> 1) branch is created >> 2) the build process is fixed so that a snapshot can be generated >> 3) the binary compatibility API numbers are prepared for a stable release >> >> if that is the case, fixing those MMODULE numbers and maybe the libganglia >> version will be all that is missing. >> > > Actually I was wrong in the previous email about the MMODULE numbers. The > MMODULE numbers don't change with versions. They only change when there is > change to the module interface that would cause an incompatibility. The > major number will change if there is an API change that would prevent any > newer module from being backward compatible. The minor number will change if > there is an addition to the module interface but that change will not prevent > a newer module from loading in an older environment. So it is possible for a > 3.2.x module to load and work in a 3.1.x environment as long as no changes to > the API have been made. As of now, there is nothing that would prevent a > 3.2.x (aka. trunk) module from loading and working in a 3.1.x environment. > So until something like that happens, we don't need to bump the MMODULE > numbers. > > I did discover that I am missing some checks with regards to loading modules > and checking the MMODULE numbers. I need to add a patch for that and then > backport it for the 3.1 branch. But that shouldn't hold anything up as far > as rolling an alpha tarball. I'll try to get that done today. > > Brad > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao > ne > _______________________________________________ > Ganglia-developers mailing list > Ganglia-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ganglia-developers ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
