Even though I clearly understand the
goal of callisto, making all the things available for download from one
update site simply augment the belief that callisto is about integration.
I think this is because the term"simultaneous release" does not
capture the motivation behind callisto (which I believe is to ease the
reconsumption of the eclipse stack for tool vendors).
So there is two possibilities:
- don't make one update site and let
people hunt down the required jars
- go ahead with one update site, fix
the obvious integration problem and get beaten by the reviews for poor
integration so we can do better the next time.
Even though it will hurt, I'm in favor
of the second option as otherwise we will never improve cross project integration
Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Callisto staging Update Site ready
fortesting ... sort of
Well, I guess the users are going to be disappointed because
I just don't see this (one update site for maintenance as well) happening
for Callisto. We'll talk about this at our next planning phone call.
But I do want to clarify: "Callisto" is the "Callisto Simultaneous
Release". There is no promise of "work together in a seamless
experience". We have been very careful not to promise that as we do
not believe that to be possible in the Callisto time frame. This is about
the "simultaneous release of the ten projects" and we will work
hard to make them work together, but there is no guarantee that that will
The user expectation is that there
will be one true update site for Callisto. All Callisto projects are supposed
to work together in a seamless experience. You can't guarantee that if
you allow multiple update sites.
cross-project-issues-dev mailing list