[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipse.org-planning-council] Re: [cross-project-issues-dev]Re-spin process
|
+1 -- agreeing with Wenfeng's point.
Regards,
John Graham
Eclipse Data Tools Platform PMC Chair
Staff Software Engineer, Sybase, Inc.
http://dataplat.blogspot.com/
"Wenfeng Li"
<wli@xxxxxxxxxxx>
Sent by: To
eclipse.org-plann "eclipse.org-planning-council"
ing-council-bounc <eclipse.org-planning-council@eclip
es@xxxxxxxxxxx se.org>, "Cross project issues"
<cross-project-issues-dev@eclipse.o
rg>, "eclipse.org-planning-council"
07/06/2007 04:50 <eclipse.org-planning-council@eclip
PM se.org>
cc
Please respond to Subject
"eclipse.org-plan RE: [eclipse.org-planning-council]
ning-council" Re:
<eclipse.org-plan [cross-project-issues-dev]Re-spin
ning-council@ecli process
pse.org>
+1 for the continuously updated distribution proposal. Especially for the
maintenance (3rd digit) stream...
Wenfeng
Second, my opinions:
Personally I like the approach where Europa is a just a name and the
content is a moving target representing the latest and greatest
versions of
the 21 projects that initially contributed until Ganymede ships. Of
course
it is harder for developers to know which versions of a plug-in
someone was
using, but the benefits for the community seems to be pretty high,
and it
also means that we regularly re-spin putting a higher burden on the
coordinator.
I like this approach a lot - it matches well with the ease of distribution
that the internet provides us.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
