> > * Someone outside of Yahoo needs to step up and start addressing the > blockers to get 0.21 released. >
Thanks for the update on the state of the world at Yahoo!, Owen--very helpful. I think the community will step up to knock down some of the blockers once we resolve what should be in the 0.21 release: the current branch, or a rebase on trunk. Do you/Yahoo! have a preference on that front? Rather than set a date, I think it is time to move to feature-based > releases. We'd need to vote on the feature set, but looking for security, > end-to-end avro, and symlinks seems like a reasonable list. That will avoid > the large rush of commits the last week of the deadline, which has been > counter productive. > Could someone give an example of a successful open source project that follows a feature-based release cycle? From the research I've done, the regular drumbeat of time-based releases seem to be more conducive to project health. Always interested to hear otherwise. The example Owen cites of "the large rush of commits the last week of the deadline" is certainly a good argument in favor of feature-based releases; I'm curious to hear more. Thanks, Jeff
