As discussed a few weeks back, I'm volunteering to manage the 3.1.3 release.
Most of the changes were made a few weeks ago now, and I've been running some of these patches on several platforms for some time, so I don't think we need to allow a lot of time for additional testing. What I'd propose is that 3.1.3 is tagged Friday as a beta, and if it is good, then we make it GA two weeks later. If problems are found, then 3.1.3 will not be made GA, and we will aim to gather feedback and release 3.1.4 in 2-3 weeks. I'm also happy to be the release manager for that follow-up release if it becomes necessary. I note that part of the release process involves setting the release name for the next release - is this up to the release manager's initiative, or are there some rules for this? ------------------------------------------------------------------------------ Come build with us! The BlackBerry® 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/devconf _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
