Clearly a year+ is too long to release, and thankfully it appears that's in the past for Lucene/Solr. But on the other extreme, one can release too quickly as well, of course. There is overhead to performing the release itself. Consequently there should be enough "goodness" in the release to make it feel worthwhile. And because we value stability and robustness in Lucene/Solr, changed code should have *some* amount of time to be potentially used and tested further. And there's impact on the user community. If a release occurred too frequently then there might be very little meaningful improvements in the release. I believe it is Hudson (now Jenkins) that followed that extreme of I think releasing every week or so. It's so frequent that as an admin of such a server where I work, I don't even care to look at what's new in the releases because there are too many of them--I've become apathetic when I was initially excited to use it. So hopefully with each release there's something truly cool to tell others about in Lucene/Solr.
Gauging these factors is of course very subjective. Personally, I think 3 months is just right, 1 or less is too fast. Given that v3.1 was released 2 months ago and there are some truly cool features like Result Grouping in Solr to announce in 3.2. I'm in favor of a release. ~ David Smiley ----- Author: https://www.packtpub.com/solr-1-4-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/VOTE-Release-Lucene-Solr-3-2-0-tp2993434p2995419.html Sent from the Lucene - Java Developer mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
