Agreed with Tom on the bundles features.
As for the p2 features, if we are going to change them and it
is low risk, why not change them now. In the precise usecase of Eclipse and
the SDK the features do not show up to the user but they may in other cases no?
For p2 vs Provisioning, I understand your point about
descriptiveness. How about
Equinox p2 Provisioning Developer Resources
Equinox p2 Director Application
Equinox p2 Generator Application
Equinox p2 Provisioning
The point of choosing a distinct name was so that we could talk
about things more easily. It was cumbersome to always say “Equinox
Provisioning”. The suggestion above does not sacrifice brevity, branding or
descriptiveness.
Jeff
From:
equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On
Behalf Of Thomas Watson
Sent: Wednesday, June 11, 2008 12:37 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] feature names
I do think the equinox bundles SDK features
should be updated for 3.4 if possible. This feature is available for download
from the equinox page. The current name is pretty strange.
Tom
John Arthorne ---06/11/2008 11:20:51 AM---I will just
point out these feature names don't appear anywhere outside our test updates
repository
|
From:
|
John Arthorne <John_Arthorne@xxxxxxxxxx>
|
|
To:
|
Equinox development mailing list
<equinox-dev@xxxxxxxxxxx>
|
|
Date:
|
06/11/2008 11:20 AM
|
|
Subject:
|
Re: [equinox-dev] feature names
|
I will just point out these feature names don't appear anywhere outside our
test updates repository apart from "Equinox Provisioning Platform".
The director and generator features are build-time only features that probably
shouldn't even be put on the test update site. They only exist because of the
nature of the build process and I don't think there are interest for users. The
p2 source feature will be installed on disk for users, but the name will only
be found by the user if they open the feature.properties file on disk, since
the source features are not installed and don't appear in the About dialog or
configuration details. Since the testUpdates repository contents will be blown
away with the first 3.5 build, I don't really see any value fixing them for
3.4.0.
I did consciously called the p2 feature "Equinox Provisioning Platform"
because I thought "Equinox p2" wouldn't be sufficiently descriptive
for a user not familiary with our code names. I could be convinced otherwise...
Having said that, consistency is of course good and it would make sense to
update them all to be consistent in 3.5 if we don't do it earlier.
|
"Jeff McAffer"
<jeff@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
06/11/2008
11:51 AM
|
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
|
|
|
To
|
"'Equinox
development mailing list'" <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
[equinox-dev] feature
names
|
|
As discussed in the planning call this morning our feature names are all over
the map. Here is a sample of some I see in the current testUpdates repo
Eclipse Project Equinox bundle feature
Eclipse P2 Developer Resources
Equinox bundle source feature
Equinox Provisioning Director Application Feature
Equinox Provisioning Generator
Equinox Provisioning Platform
The should be… (in the corresponding order)
Equinox Bundles
Equinox p2 Developer Resources
Equinox Bundles Developer Resources
Equinox p2 Director Application
Equinox p2 Generator Application
Equinox p2
Anyone have other ideas?
Jeff_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
