|RE: [cross-project-issues-dev] Callisto staging Update Site readyfortesting ... sort of|
If it's just about "the reconsumption of the eclipse stack for tool vendors" then what do we need an update site for? Tool vendors can deal with humongous zip files. Tool vendors can deal with weird version dependencies. I thought the main idea of an update site was to improve the experience for end users.
So how about option 3:
- Have one update site, make the integration good, get good reviews, *and* do synchronized updates ala IDEA and NetBeans. (I know it's more than an IDE but having it be a super IDE gets it in the door for the other things).
Once the update site is working you'll have about 3 months for integration polish, with community feedback.
Back to the top