I am thinking that something is missing in our Heresy conversation, what is the user experience supposed to be?
On June 25 we release the Ganymede simultaneous release. What is the recommendation for Europa users? Do they junk their existing Eclipse install and download a new package? Or do they use update?
If we agree to "use update", then do we not want to point them to one update site?
Has anyone actually tried "upgrading" the existing Europa packages?
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development Manager: Eclipse Open Source Components
IBM Rational Software: Aurora / GMF / Modeling Tools
"Jeff McAffer" ---04/29/2008 05:01:45 PM---1. Originally the annual simultaneous release was all about coordinating releases. Just that, nothin
"Jeff McAffer" <jeff@xxxxxxxxx>
"'Cross project issues'" <cross-project-issues-dev@xxxxxxxxxxx>, "'eclipse.org-planning-council'" <eclipse.org-planning-council@xxxxxxxxxxx>
04/29/2008 05:01 PM
RE: [cross-project-issues-dev] Heresy mark II (summaries and replies)
1. Originally the annual simultaneous release was all about coordinating releases. Just that, nothing more: coordinating the releases so that all the projects could release on the same day.
These points are valid but they are the implementation of a greater goal that was to ease the lives of consumers. To make it easier for them to get a consistent lineup of Eclipse function that at least was thought to work together. I don’t recall ever liking the idea of sending consumers all over eclipse.org to get what they need.
2. Originally (pre-Callisto) our goal was to have a single update site that merely *referenced* the existing project update sites. No file copying, no archiving, no building - just references so that our testers could point their update manager at a single update site url.
First, where the files live is not the issue as long as the end user only has to type in one URL.
- "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" -- because they are two different activities: copying multiple update sites into one update site is different from using multiple sites to build an Eclipse instance. Ganymatic does not attempt to load all the plug-ins nor does it run any tests. The end users care about those issues, not whether all the files live in one directory or ten.
If all Ganymatic does is copy files, how does it fail and why is it so much work to run/maintain? That is an honest question. My assumption is that if something that fails in Ganymatic it is somehow going to fail for end users. I realize that the reverse may not be true (e.g., working in Ganymatic does not necessarily imply it will work for the user) but some coherence checking is better than none.
cross-project-issues-dev mailing list