I'm not totally agree with your point. Since we are a mature project (not incubation) we can't allow to ourself to declare API as a malfunctioning, and just remove it. We have to think about potential adopters or commiters.
2008/6/26 Roy Ganor <[EMAIL PROTECTED]>: > Since 1.0.x branch contains all this information (and can be used as a > reference) and since the old model is malfunctioning rather than deprecated > (as explained in the previous email) and since the malfunctioning model > takes lots of lots lines of code there is no reason to keep it alive. > Moreover I don't want that people use it incorrectly, they should search for > a reference in the JDT or DLTK platforms. As my previous email says it is a > necessary move rather than desirable. > > > > About the versioning matter, I do agree with Nick, we should call this > version 2.0. Guy (the project leader) is going to decide how to handle this > from here. > > > > Thank you for the feedbacks! > > BTW – have you seen this incredible demo? > http://www.searchenginecaffe.com/2008/06/eclipse-ganymede-simultaneous-release.html > > > ------------------------------ > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Seva Lapsha > *Sent:* Thursday, June 26, 2008 12:59 AM > *To:* PDT Developers > *Subject:* Re: [pdt-dev] PDT 1.1. - API updates following infra changes > > > > Roy, > > Can you please share some draft document (e.g. a wiki page) to explains > main points of the issue before the first session? > > Regards, > Seva > > 2008/6/25 Roy Ganor <[EMAIL PROTECTED]>: > > Consulting with other committers, it is important to have a discussion > about the new API. > > Two sessions will be held (scheduled later) about the API change, the first > one to collect feedbacks and the second to present the final API. > > > ------------------------------ > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Roy Ganor > *Sent:* Wednesday, June 25, 2008 1:24 PM > *To:* PDT Developers > *Subject:* [pdt-dev] PDT 1.1. - API updates following infra changes > > > > Hello there, > > > > Unavoidable step following our infra changes is to change Eclipse *PDT 1.1 > * API. > > Yes, it is a necessary step rather than a desirable one, we first thought > that we could write adapters to the old model but the ROI is low. In order > to step forward we must "slice" the cake and make a few changes. A detailed > document about our new API should be delivered shortly after we finish the > migration work. > > > > The following extension points will be replaced with our new API: > > 1. org.eclipse.php.core. includePathVariables > 2. org.eclipse.php.core.modelFilter > 3. org.eclipse.php.core.phpBuilderExtensions > 4. org.eclipse.php.core.phpModelExtensions > 5. org.eclipse.php.core.workspaceModelListener > > > > Regards, > > _______________________ > Roy Ganor > Team Leader, R&D > tel. +972-3-7539637 > mob. +972-52-3290-754 > Zend Technologies Ltd. > > > > > > > _______________________________________________ > pdt-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > > > _______________________________________________ > pdt-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/pdt-dev > > -- Michael
_______________________________________________ pdt-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/pdt-dev
