I disagree to some extent. Yes, the features need to be stable and useful, but it sure helps if some subset of them tell a story.
We learned this with Ultraseek. We had a great set of features in one release but no story, so people weren’t interested in it. After that, we intentionally chose a theme for each release. If we want people to upgrade, let’s make it easy for them to understand why. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Sep 10, 2025, at 4:36 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > > : >> If we don't ship headline grabbing features in a major release, we might > as > : >> well abandon this project and dedicate our focus on building OpenSearch > or > : >> Elasticsearch. > : > : This brings up memories of the tragedy of Perl 6. > > +1. > > Features should be added because they are useful & desirable. > Features should be released when they are ready & stable. > > Our primary concerns for what changes go into each (semanticly) versioned > release should be based on stability, back compatability, and forward > compatibility -- not what kinds of headlines they will generate. > > > -Hoss > http://www.lucidworks.com/
