[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[platform-update-dev] Callisto Discovery Site
- From: "Daffin, Miles (IT)" <Miles.Daffin@xxxxxxxxxxxxxxxxx>
- Date: Fri, 21 Jul 2006 10:32:16 +0100
- Delivered-to: email@example.com
- Importance: normal
- Priority: normal
- Thread-index: AcasqI5QBINmHp0oS8iilLn3D/8cJQ==
- Thread-topic: Callisto Discovery Site
Thanks for all yor
help thus far. However I am still pondering the best way of implementing update
sites at my firm. I have 4 related questions.
The plan at the
moment is to have one update site for Homegrown plus various Open Source and
Vendor features. We will also have a number of mirror sites for trusted 3rd
parties (e.g. Callisto, Eclipse Project, MyEclipse).
Callisto Discovery site seems to be more than just a plain update site. It seems it is in
some way aggregating update sites within itself. If you install an update
from Callisto more update sites appear in your list after
restart. If possible I would like to use this approach at Morgan Stanley.
Does anyone know how this
can we prevent users updating directly from sites like Callisto? (Can update
policies cover multiple sites?)
- For internally
created update sites, is it better to build them using an Eclipse IDE Update site project or in some other
way? (The Eclipse
docs on this are pretty
- We need a change
control process for updating the update
sites. Right now we are thinking we will update a mirrored update site
in a staging area, get this tested by a group of beta testers and then turn
the beta site over into production
if there are no issues. Any information on such a managed process would be
I am not asking too much.
Morgan Stanley | EAI | MSDE
20 Cabot Square | Canary Wharf | London E14 4QA |
Tel: +44 (0) 20 767 75119
NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited.