Markus,
I read your (well written) comment on the bug, and I understand the
path of reasoning that it follows. However, I want to point out
that, even though it's a small percentage, the shared-install users
WILL be annoyed at this and I suspect at least few of them will be
quite vocal about it. We must learn a lesson from the Java 1.6u21
debacle, that lesson being the PR hit we can take, even when there
are work-arounds and help available, can be sever.
Believe me, I'm a purist at heart, someone who usually values
"cleanliness" above all else; the idea of including some bundles for
no other purpose than to avoid a broken previous build is not
pleasant. But I'm also a community advocate, and I don't want to
have to answer yet another question about "why doesn't Eclipse
work?" to users. The reputation hit shouldn't be discounted.
I don't understand the point about unknown side effects; don't we
have time to thoroughly test the update scenarios so that we feel
confident there are no unintended side effects?
It seems we have two paths, one that is the "clean" approach, but
leaves some users in the lurch and hopes that they will know where
to go for help and have the/time patience to get it. The other
option is less clean but is transparent to everyone. It's a
difficult decision to choose between them, but I would opt for the
one that is transparent so long as there's a way out of including
the extra bundles forever (which, IIUC, there is since the latest p2
component won't need them).
Eric
On 9/13/10 10:30 AM, Markus Knauer wrote:
In
order to keep you updated about the progress with the Helios SR1
RC3 packages:
In comment #21 of bug 322929 (see [1]) I tried to sketch my
proposed solution for the configuration problem in shared installs
of the EPP packages. My own focus has changed and my top priority
is now to deliver SR1 packages that do not contain the problem any
more (of course), but also not to include bundles in SR1 just
because there were problems in the June release. My feeling is
that this is too risky and that we should not change the
configuration of the packages between the release and a service
release. On the other hand that decision means that we need to
educate some users that are using EPP packages in a shared install
and are trying to update to SR1. More information and comments
should be done on the bug.
The current status is that I now have a new metadata repository
available based on this proposal. It can be found here [2] and is
being used for the packages that a still building [3]. I will ask
the package maintainers later today to test and sign off this
build.
Thanks and regards,
Markus
[1] Bug 322929
- EPP configuration problem
prevents shared installs from working
[2] http://download.eclipse.org/technology/epp/packages/helios/SR1.233
- p2 repo
[3] http://build.eclipse.org/technology/epp/epp_build/36/download/20100913-1410/
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
|