Hi, Just to be clear: IMHO a burden on a small number of developers (namely definers of API and implementors of that same API) is much preferable to burdons placed on our users !
We are the specialists, we know more, so we should be able to do more and bury an additional burden. It is, in fact, not a big one for us. We just have to get used to it ... So no matter whether we have tooling or not, it is IMHO our task to take that burden. As I said, the main cause of issues in Sling is probably the Sling API bundle. Regards Felix Bertrand Delacretaz schrieb: > On Tue, Nov 17, 2009 at 9:24 AM, Carsten Ziegeler <cziege...@apache.org> > wrote: >> ...Again, with proper tooling all of this is no problem.... > > And we don't have such tooling, or do we? > > I see the logic in Felix's reasoning, but without tooling I think the > burden on developers (and on users trying to make sense of a myriad > version numbers) is too high. Not because we are too lazy to do it, > but because more work means more room for failure. > > As for tooling, something that computes digests on the source code of > packages, and checks that the version numbers change when the > aggregated digests of a given package change, would at least make it > possible to know when package version numbers need to change. > > Also, maybe this version management scheme makes sense for a small > number of our bundles (like the API bundles), in which case we might > agree to use this scheme just for those few bundles - which also > rarely change, making that more manageable. > > -Bertrand >
