That's not quite what I meant. I didn't mean the committers on the project, I'm not really worried about other's interest in the project. I'm invested enough myself in the project that I would keep it going by myself if I needed to, although I already know that the others are invested as well, and that would never happen.
When I was talking about users, I meant the users of the library who use it in different products. This would include the open source projects like RavenDB and Orchard, as well as commercial users like StackOverflow. We've heavily broken backward compatibility from 2.9.4 to 3.0.3, which, depending on the scope of user's projects, can be a large upgrade task. To abandon future versions of that branch, which would likely require few code changes for our users to upgrade, might not be in the best interests of the project. The 4.0 branch is fantastic, and as I said before, we had in the past expected to have, like our java counterpart, two branches worked on in parallel, one for the 3.x and 4.x branches. However, as life has gotten in the way for all of us, many are unable to put in the amount of time we originally wanted to in the project. So that might not be a possible solution anymore. I'm NOT saying that skipping out of 3.x and moving to 4.x is the wrong thing to do. In fact, it might be what we need to do to spark more interest in contributers. The bottom line is that everyone in the PMC needs to discuss it before we make any decisions. Thanks, Christopher On Mon, Oct 29, 2012 at 10:34 PM, Michael Mitiaguin <[email protected]> wrote: >>That leaves the question of whether it would alienate our users to abandon >> the 3.x branch in favor of working solely on the 4.0 release. > > My understanding, by users you meant developers ( committers ) who are > involved and already spent some time on 3.6 branch Unless 3.6 is the final > one for Lucene.Net ( hope not ) , PMC members could vote or at least > discuss a feasibility . Quite possible, some people after releasing 3.6 > won't be interested to do it again for V4. There is a chance to decrease > the gap between Java and Lucene.Net counterpart , as Java V4 has just been > released. > As for real users like myself, certainly, I'd prefer to get Lucene.Net V4 > earlier and not to have 3.6 at all.
