Hi, On Wed, 2016-09-28 at 22:07 +0000, Stefan Seifert wrote: > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > we have the goal to do sling releses more frequently, perhaps 4 per > year.
+1, sounds good to me. If anything, I would like to prevent situations where people where trying to run Sling on Java 6 and it failed since we hadn't release in quite some time. > 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. +1 > > 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. https://cwiki.apache.org/confluence/display/SLING/Releasing+a+new+versi on+of+the+Sling+Launchpad > > it would be good to have a docker image for each sling release as > well. this should not be complicated. This is also documented in the wiki page above. Well, a link to a README.txt :-) . Robert
