On Tue, Oct 27, 2009 at 10:15:15AM +0000, Daniel Pocock wrote: > Carlo Marcelo Arenas Belon wrote: >> >> DragonFlyBSD fails to build (tested with 2.4.0 32bit). >> > how do you propose we avoid missing stuff like this in future?
Not sure if this can be avoided, but there might be some things we could do to mitigate like : * periodic snapshot releases * automated buildfarm * census of developers/users which could help with testing per platform * some sort of unit tests or other tests which could be automated > 3.1.3 was floating around for a while, and I tested it on RHEL3, RHEL4, > RHEL5, Solaris 8, Solaris 10, Debian lenny and Cygwin. And that was very useful as it uncovered a problem in RHEL3 AFAIK. > Do you think we need some checklist of supported platforms that must be > verified before we tag in future? The release notes includes a list of supported platforms which usually reflect the ones that we got reports were working fine during the testing cycle. My objective with this report was to let you know that DragonFlyBSD wasn't one of them. I wasn't implying that report was to be considered as a showstopper for the release either. > We may need to have some buy-in from > people willing to run the tests at short notice as a release date > approaches, as not many people are going to have easy access to every > supported platform. And not all people will be available either. > Maybe commits on the release branch need to be blocked while such > testing is done? This already happens AFAIK even if there is no formal provision against it, but just to simplify the release manager job who would need otherwise to cherry-pick a release branch. Setting up a list of objectives before the release is tagged might help though clarify what is expected from the release (including clarification of which areas will need testing or which features are to be evaluated) and also which platforms are expected to be supported based probably on feedback provided from pre-release packages. Carlo ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
