I have always, since day one, seen the train as a facility for
our consumers (ISVs, integrators and end-users). People used to have to
hunt around, randomly pick version and then hope that they got it right. They
never did. There are plenty of comments, notably by Ed Burnette, about
the pain of pre-train days.
The packages are fantastic. Many people get them and just
use them and never need anything else. However, the Eclipse community offers much
more. Making it easier for consumers to discover and acquire these other
things in a coherent way is, IMHO, what the train is/should be about.
I don’t dispute that putting together the update site is
challenging but it seems that eliminating the Ganymede site is in effect asking
the entire community to do that hard work on their own and independently?
That is, if we can’t manage to aggregate a set of update sites into one,
how do we expect end users to aggregate content from multiple sites into one
Eclipse configuration?
Jeff
From:
cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Schaefer,
Doug
Sent: Monday, April 28, 2008 9:55 PM
To: Cross project issues
Subject: RE: [cross-project-issues-dev] Notes from a Heretic: Why do we
havethe Ganymede update site?
You know having been there since day one, the update site isn't
what the train is all about. The update site is a quick way to allow us to test
that all the plug-ins load together and don't break anything major. That's what
the train is all about. At least it was until it took on a life of it's own...
Doug.
From:
cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff
McAffer
Sent: Monday, April 28, 2008 3:50 PM
To: 'Cross project issues'
Subject: RE: [cross-project-issues-dev] Notes from a Heretic: Why do we
havethe Ganymede update site?
Burn him!
I will echo the other opinions in favour of continuing to have
the release train update site. This is the one stop shop that is what the
train is all about. Packages are not everything. Project update
sites can quickly get populated with other stuff that is not part of Ganymede.
End users (aka the unwashed masses) will be confused if they have to go
multiple places. The developers (aka us) know what’s going on and
the semi clean/dirty may get a bit confused but likely know enough to sort it
out.
Jeff
From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Bjorn
Freeman-Benson
Sent: Monday, April 28, 2008 7:40 PM
To: eclipse.org-planning-council; Cross project issues
Subject: [cross-project-issues-dev] Notes from a Heretic: Why do we have
the Ganymede update site?
Ganymede Project Leads,
Let me open a can of worms and publicly ask why we have the Ganymede Update
Site.
It seems to me that:
- If we have packages, why have a separate
update site? The packages have all the update sites built in (via
the feature.xmls).
- And if someone wants to add new
functionality to their existing Eclipse, they will go to the project
specific update site and get the latest bits.
- For adopters, we have the project downloads and
update sites - why should we have a second update site for these?
- In fact, having a second update site just
makes things more complicated because then "where do I get future
updates? do I get them from the central update site or from the project
update site? and why are there so many similar update sites listed in my Eclipse?"
- More complicated for project teams too,
because then they have to maintain different site.xmls, feature.xmls,
etc.
The original reason for the unified update site was because
it was confusing for users to have to go here and go there and go the other
place to put together a package. But now that we have packages, why do we need
the unified update site? It seems to be extra hassle and complexity for
everyone at no net benefit to anyone.
Comments? Opinions?
- Bjorn
|
