| RE: [eclipse.org-planning-council] A suggested topic for Planning Council Discussion |
|
The point is to raise the quality
perception of Eclipse in the marketplace, i.e., beat NetBeans (and for my
community, be as good as Visual Studio). Nothing changes to the train and its
current operation. This is more an addition for those projects who want and
need to work at addressing these issues. The process for managing these products
needs to be open just like everything else in Eclipse. But depending on what we’re
trying to achieve strategically, some components would end up not making the
cut, just like in the “real” world (been there, done that, i.e.
been cut, its just part of doing business). Doug Schaefer, QNX Software Systems From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of Scott Lewis Doug Schaefer wrote: Yes. Allow any project to release along with the train as far
as scheduling and the monster update site go. But create a second tier of
product quality components that would be released as part of the EPP packages.
|