Do it, if you need it. +1


Le 10/05/11 20:02, Lombard, Scott a écrit :
+1

-----Original Message-----
From: Troy Howard [mailto:thowar...@gmail.com]
Sent: Monday, May 09, 2011 4:05 PM
To: lucene-net-dev@lucene.apache.org; lucene-net-u...@lucene.apache.org
Subject: [Lucene.Net] VOTE: .NET 2.0 Framework Support After Apache
Lucene.Net 2.9.4

All,

Please cast your votes regarding the topic of .Net Framework support.

The question on the table is:

Should Apache Lucene.Net 2.9.4 be the last release which supports the
.Net 2.0 Framework?

Some options are:

[+1] - Yes, move forward to the latest .Net Framework version, and drop
support for 2.0 completely. New features and performance are more
important
than backwards compatibility.
[0] - Yes, focus on the latest .Net Framework, but also include patches
and/or preprocessor directives and conditional compilation blocks to
include
support for 2.0 when needed. New features, performance, and backwards
compatibility are all equally important and it's worth the additional
complexity and coding work to meet all of those goals.
[-1] No, .Net Framework 2.0 should remain our target platform. Backwards
compatibility is more important than new features and performance.


This vote is not limited to the Apache Lucene.Net IPMC. All
users/contributors/committers/mailing list lurkers are welcome to cast
their
votes with an equal weight. This has been cross posted to both the dev and
user mailing lists.

Thanks,
Troy

This message (and any associated files) is intended only for the
use of the individual or entity to which it is addressed and may
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient
you are hereby notified that any dissemination, copying or
distribution of this message, or files associated with this message,
is strictly prohibited. If you have received this message in error,
please notify us immediately by replying to the message and deleting
it from your computer.  Thank you, King Industries, Inc.

Reply via email to