I think the versioning scheme is OK, as it supports the needed requirements.
I very much like the idea of just releasing single bundles, as it allows faster bug fixing and improvement/enhancement of funtionality. But from a user perspective it should be ensured that there are regular releases of webapp and standalone app. On the one hand this allows releasing of a set of bundles wich are ensured to work together. On the other hand it prevents users that start with sling in one or two years from starting with an old sling version and installing all new bundles again. BTW, is there a way to define a set of bundles which certainly work together. Can this be done with the assembly feature? If so we could just release assemblies containing newest sling bundles once or twice a year. Regards Alex Felix Meschberger schrieb: > Hi all, > > I have been thinking about releases and version numbers in Sling and > wrote up an initial text on that at [1]. > > The page is currently missing the actual list of bundles, we would want > to include in the initial release. This is something, which still has to > be defined. > > WDYT ? > > Regards > Felix > > [1] http://cwiki.apache.org/SLING/thoughts-on-release-management.html > >
