So it's my understanding that the Sling 'releases' are along the lines of a snapshot in time of the core bundles. It provides an opportunity for someone to try out the latest Sling stuff and to publish API's but it's not really a product/project release.
The actual product is the sling starter which defines the bundles that defines the release. I would love to see someone create a supported Sling release, kinda like CRX back in the day. One that you could go to and download and you know you're getting a stable set of bundles, and that will do point releases if a bug is discovered. That sort of thing. - Jason On Tue, Jul 31, 2018, at 8:22 PM, Daniel Klco wrote: > Theoretically, sling is a sum of the installed bundles so you could create > a Jackrabbit package that updates the bundle versions on an existing > instance. > > It would really be up to the end application developer to support such an > upgrade mechanism. > > I'm not sure this would work for all version updates (ex: breaking changes > like going from Jackrabbit 2.0 to Oak) but it should work for most. > > > On Jul 31, 2018 7:10 PM, "Andreas Schaefer" <[email protected]> > wrote: > > Hi there > > I was just wondering if there is a way to upgrade to a new version of sling > like 9 to 10 without having to export and import my content / configuration. > > If I have a blog like Slick or a website using Peregrine and I want to > upgrade to a newer release of Sling exporting all my content might be an > end user nightmare. > For example I can easily upgrade my Wordpress site to a newer version. > > Thanks - Andreas Schaefer
