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.
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Bjorn
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
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
- 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
- More complicated for project teams too,
because then they have to maintain different site.xmls, feature.xmls,
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.