Hi, [X] -1 No - Flume should adopt some other policy
I believe marking the artifact with a beta label creates the expectation that there will be a final release later. Also, this sets a precedent for having to get the community into agreement about what beta vs. not beta means. I think all of this gets in the way of creating a rhythm of regular releases and is overly subjective. It would be more productive to give people information so they can make their own judgment of whether Flume meets their needs. Known issues should be filed in JIRA, and noted on the Flume web site if they are thought to be significant to the release. If there are criteria we should pass before release, those should be encoded in unit tests and/or automated system tests. General recommendations / thoughts about how it should be used should go on the web site. Regards, Mike On Mar 19, 2012, at 12:10 AM, Ralph Goers wrote: > I would like to propose that Flume adopt the release numbering scheme > followed by Apache Commons which can be found at > http://commons.apache.org/releases/versioning.html#Release_Numbers. > > Please vote > > [] +1 Yes - Flume should adopt this policy > [] +0 Abstain - I don't have a preference > [] -1 No - Flume should adopt some other policy > > Ralph
