discussed at the Sling Committer Round Table @ adaptTo() 2016 we have the goal to do sling releses more frequently, perhaps 4 per year.
it should be made easier to release sling. this would be the case if the launchpad is split into a stable and unstable part (see separate thread), and the integration tests are always compatible with the latest released bundles. we want to stick with the current version numbering - just using a single major version increased on each release. it is by intention that this version has no meaning besides indicating which release is newer. steps like generating consolidated javadocs is already automated. i'm not sure if the excact step for doing a sling release are already documented somewhere. it would be good to have a docker image for each sling release as well. this should not be complicated. stefan
