On Wed, 2016-09-28 at 22:06 +0000, Stefan Seifert wrote: > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > currently we have only one launchpad in trunk, which contains a > mixture of release dependencies and snapshot dependencies. this makes > it difficult to release new versions because one has to release all > snapshot projects first, and perhaps the last relese version is fine > as well. > > we came up with a new proposal to fulfill the different needs: > > - the launchpad maintained in trunk should always be the "stable" > launchpad, referencing only released dependencies of the sling > bundles and oft the integration tests project > > - the "unstable" launchpad is created dynamically from this stable > launchpad by using the same bundle list, but for each dependency the > latest snapshot version that is available in the maven repo, > including the latest snapshot version oft he integration tests. > perhaps the slingstart plugin could be extented to generate this. > > - i'm not sure what to do with new bundles which are not released yet > thus are not referenced in the stable launchpad.
I'm +1 on this change, it makes it much simpler to perform releases. If we make building an unstable launchpad really simple, e.g. an addition profile or a mojo property, I don't think we lose anything. Robert
