| RE: [cdt-dev] Indexer policies voting |
|
Ø
The
“line” has to be drawn somewhere, and in the Eclipse charter,
it’s the committers that do that. Ø
YES!!! It is so refreshing to have the developers
be on top of the food chain instead of … 8-) Decisions can be made on technical merits
this time around. For the indexer policy, there were lots of
PRs(read complaints) on this subject. Folks have ask, to make it(the indexing)
an action on a folder, by disabling the indexer on the project and selectively
choose the container to indexed, it gives more flexibility and help scalability
for folks with weird projects structures/files. Moving this to CDT-3.1
instead of 3.0 will allow us to gather more feedbacks and better understanding
on how to solve this. And maybe see why the indexer is so slow. Agreed, currently, the impact of the
indexer on the CDT users is serious. From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Treggiari, Leo > The question is how this impacts the
customer! There are many customers and many new
features in CDT 3.0. If we were to hold off on CDT 3.0 until we had all
of the enhancements that people want implemented, there may never be a CDT
3.0… ;-) The “line” has to be drawn
somewhere, and in the Eclipse charter, it’s the committers that do that. Regards, Leo From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Herriot, Nicholas, VF UK -
Technology (TS) The question is how this impacts the
customer!
|