Hi, On Thu, Jun 5, 2008 at 12:41 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > I hope this is ok for everyone?
OK, with one concern: > e) All upcoming releases will be single bundle releases. I'm a bit worried about this. Even though Sling consists of multiple components, from the end user perspective it's still a single product, and it would be good if that was at least somehow reflected in our releases. For example, how do we identify the Sling version that is deployed somewhere? The collection of the versions of all the deployed bundles? Where and how can I find all the Sling source code that went in to that deployement? I'd rather not have to trace down the entire dependency tree to find all the relevant source packages. One could argue that all the required information is in the Maven repository and there is already good tooling to manage that information, but I'm still somewhat hesitant to rely on the repository so much. Perhaps I'm just being old-fashioned and this won't matter in practice, but I still feel we're loosing something valuable here. At least this is another good example of how Maven and the Maven repository are taking a much more essential role (i.e. not just another build tool) in release management and even changing the meaning of a "release". It'll be interesting to see where such progress takes us and how well for example the Apache release practices will cope with this change. :-) BR, Jukka Zitting
