Re: [eclipse-pmc] Requesting approval for move of bundles from e4 to pla

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

Sigh. Renaming bundles and packages
hadn't been considered (until today). One advantage of this designation
in the Platform project is that unlike every other project at Eclipse,
we currently have no "third segment" designation at all for the
Platform project. This causes us to pollute the top level org.eclipse.*
namespace that needs to be shared across all Eclipse Foundation projects,
and makes it difficult to determine the project ownership for the bundles/packages
we produce (for everything else at Eclipse, the third segment tells you
what project it belongs to).  So leaving the "e4" segment
in there would be a good outcome from this perspective. Although it means
org.eclipse.e4.* could belong to either e4 or Platform projects, and you'd
need to check the incubating status to be sure which project it belongs
to.

On the other hand it does somewhat confuse
the meaning of "e4". e4 was always about "creating the next
generation of the Eclipse platform". Now that the next generation
is arriving, I'm not sure how the e4 incubator should be marketed/branded.
>From a brief discussion with McQ he suggested the e4 incubator should now
be about creating technology for the 4.x generation of the platform as
a whole. From that perspective having "e4" in the bundle names
for that generation of the platform doesn't seem too bad.

More pragmatically, renaming bundles
and packages this close to the release would be costly. If we simply deleted
the "e4" segment, we would overlap in some cases with existing
bundles/package names in the 3.x generation (for example org.eclipse.ui.workbench
vs org.eclipse.e4.ui.workbench). We would need to come up with new names
for several bundles/concepts to avoid confusing the 3.x version from the
e4 version. This would also make it difficult for clients to distinguish
the two generations of technology (there are a few people trying to create
"pure e4" applications who would now have a much more difficult
time figuring out exactly what that means). A typical project move would
just involve renaming the third bundle/package segment rather than removing
it.

Overall I'm torn. I can see the problems
it causes, but I think the rename would be too disruptive to our release
to do it now, and introduces some new problems as well. If we think the
overloaded meaning of "e4" is a big enough problem, I'd be tempted
to rename the incubator after the 4.0 release rather than rename the maturing
technology.

John

Mike Wilson/Ottawa/IBM@IBMCA
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

06/25/2010 09:12 AM

Please respond to
eclipse-pmc@xxxxxxxxxxx

To	eclipse-pmc@xxxxxxxxxxx
cc
Subject	Re: [eclipse-pmc] Requesting approval for move of bundles from e4 to        platform

Thanks for putting this together, John.

At the risk of creating a lot more work for ourselves, have we considered
removing the "e4" designation in the package names as part of
the move?

McQ.

John
Arthorne---2010/06/24 02:50:43 PM---As discussed in the past, we would
like to move several bundles out of e4 into Platform, in order to process
a 4.0 release this

From:	John Arthorne/Ottawa/IBM@IBMCA
To:	eclipse-pmc@xxxxxxxxxxx
Date:	2010/06/24 02:50 PM
Subject:	[eclipse-pmc] Requesting approval for move of bundles from e4 to platform

---

As discussed in the past, we would like to move several bundles out of
e4 into Platform, in order to process a 4.0 release this summer. The first
step in the formal process is to have a "Move Review" to obtain
Eclipse Foundation approval to move the affected bundles from e4 to Platform.
A prerequisite to that review is to receive official, documented PMC approval
for the move. As such, I am requesting approval from the PMC for this move.
Details on precisely what is moving and what committers are affected can
be found here: 

http://wiki.eclipse.org/E4/4.0_Release_Process

Please vote and/or discuss. We can also discuss this on the call next week
if desired, but given all the holidays I thought it best to start the process
on this list. 

+1 from me, obviously ;) 

Thanks, 
John_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc