> 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)
Sent: Thursday, July 21, 2005
10:56 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] Indexer
policies voting
The question is how this impacts the
customer!
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx]On Behalf
Of John Camelon
Sent: 21 July 2005 14:27
To: CDT General developers list.
Subject: Re: [cdt-dev] Indexer
policies voting
-1 for 3.0. Too late. Aside from
introducing new UI, it multiplies our testing of all indexer related features
by number_of_policies.
JohnC
www.eclipse.org/cdt
cdt-dev-bounces@xxxxxxxxxxx
wrote on 07/21/2005 09:11:58 AM:
>
> CDT developers,
>
> I call you to vote whether fix for PR 104583:
[Indexer] Implement
> indexer policies
>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=104583
>
> makes it in for CDT 3.0 or not.
>
> My vote is +1.
>
> Thanks,
> Vmir
_______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/cdt-dev
