> Guys, stop this endless and pointless thread. You're both right. or don't, if you think it helps keeping Lucene ecosystem healthy at the level we are used to :) From another perspective, strong emotions are only a signal to everybody that someone cares, and that's good!
one side comment from the user perspective. /trunk in Lucene world is not really unstable, newer was. We are happily running trunk in production for many years now. We simply decide ourselves which commit needs more baking and do our own tests. In any case, we users thank you for, imo, one of the best open source projects. On Sep 13, 2013, at 2:10 AM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : Guys, stop this endless and pointless thread. You're both right. You > : should not have unstable code in a stable branch, that should be on > : trunk. This said, you should not spring out RCs without warning. Some > : stuff may actually be in trunk ready to be merged if you give a heads > : up, or some stuff may have just been merged and have had a merging issue > : causing problems on the branch, so could be fixed or reverted with > : proper warning. > > +1 > > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
