Hi,
Bertrand Delacretaz schrieb:
On Thu, Jun 26, 2008 at 9:32 AM, Jukka Zitting <[EMAIL PROTECTED]> wrote:
...As far as I've understood, the plan going forward is to have separate
release cycles for all Sling components....
By default, Sling users are expected to use the "big" Sling releases,
for example what's under [1] for the current release, which is also
available as app and webapp binaries.
I am not sure, we should or can say "Sling users are expected to use the
"big" Sling releases". We can certainly say, first-time users should use.
I envision the big releases to just be convience to the uninitied -- not
all users are uninitiated ;-)
For more experienced users, updating per bundle is much more convenient.
For this we should have the OSGi bundle repository (as I already said),
which enables this simple update.
For example: If you update your Sling instance to the latest Felix
WebConsole and Felix bundlerepository snapshots you may go to the OSGi
Repository page and add the repository:
http://people.apache.org/~fmeschbe/repository.xml
This is a prototype master repository which referrs to a prototype
Apache Felix repository and the Sling repository. After adding this
repository you get a list of all bundles provided by these repositories
which are either not currently installed or which are updates of
currently installed bundles.
Likewise on the bundles page you should see the "Update" buttons of
bundles with more recent version(s) in the repository being active.
Regards
Felix
