Rather than me continuing to ask if we are ready to create the 3.1.x stable branch, I have created a STATUS file and added it to the root of monitor-core. We talked about the usage of STATUS file during the developers' meeting in Feb. The primary purpose of the STATUS file is to capture two things, showstopper issues and backport proposals. However the backport proposal section is only relevant in the context of a stable branch rather than for TRUNK. So until the 3.1.x branch is actually created, the main purpose for the STATUS file will be to capture issues that need to be resolved before we can create the branch. As a side note, please feel free to add any other information to the STATUS file that will help to indicate the current state of the code.
Here is how it should work. Please add any issues to the STATUS file that MUST be resolved before we can create the stable 3.1.x branch. Keep in mind that the state of the code does not need to be release quality in order to create the branch. The state of the code simple needs to be buildable and functional (within reason). The purpose of the branch is to get to an initial stable state and then to maintain stability throughout the life of the 3.1.x release. Issues that MUST be resolved before creating the stable branch are issues that would cause incompatibilities between versions within the branch. Since 3.1.x has not released anything yet, incompatibility isn't really an issue. When an issue has been resolved, then the entry can be removed from the STATUS file. Once all showstopper issues have been resolved, then we can create the branch and move forward with stabilization and the first release. Also keep in mind that as soon as we create the branch, the branch will fall under the Review-then-Commit rules in the same way as the 3.0.x branch is now. So please identify and add to the STATUS file any issues that MUST be resolved before we create the branch. Then let's work at getting these issues resolved quickly, creating the branch and releasing a BETA from the branch. Brad ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
