On 3/15/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
On 3/15/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote: > 2007/3/15, Nathan Bubna <[EMAIL PROTECTED]>: > > Once the fix/feature/whatever is in an official > > release, then those issues can be closed. > > Ok, then when a release is considered "official"? Has it anything to > do with its quality (test build, alpha, beta, GA)? > Sorry for this question, but I am eager to understand :-) a release is official when it gets three PMC +1s and the release manager makes it public (user list announcement, links on the download page, etc). these are the milestones that mark the progress of the project, and thus they make convenient times to close issues. a release is not official when it is just a test build (only announced on dev list, or found in some nightly snapshot directory, etc). these are just candidates for being milestones and may not pass muster.
The distinction is simpler than that. A release, being something voted on by the PMC, is official by definition. A test build is *not* a release. -- Martin Cooper
Antonio >
