Thx for the hard work Zoe. I really think for such things, using a wiki would be better than a web site.
Throughout the web page, you refer to "semantic versioning of bundles", but afaik, there's no such thing. Semantic versioning defined is at the package level, as that's where the constraints are put, not on the bundle version. So if we don't release per bundle (i.e. we release the whole thing or per component), I don't think we have to have different versions between a single release. That would mean we could release a bundle v 1.0 with a package v 2.0 and later the same bundle in version 1.1 with a package v 3.0 or on the opposite, a bundle in version 2.0 with a package in version 2.1. I think if we follow semantic versioning, the package version and bundle version can / should be completely untied. On Wed, Feb 9, 2011 at 18:33, zoe slattery <[email protected]> wrote: > Hi > > I started to pull together both the requirements, information about what we > do already, extracts from some discussion on the mailing lists and assemble > them into a web page. The page is here > http://aries.apache.org/development/ReleaseProcessRequirements.html > > I used a web page because I was having difficulty writing it down without > diagrams, so I thought we needed something with pictures. > > I have not attempted to reach any conclusion - I've just tried to list > advantages and disadvantages as clearly as I can. > > I would like to discuss the content of the page on this mailing list, > principally I would like to understand what advantages and disadvantages I > have missed in each case. I will update the page based on feedback on this > list. Eventually, the web page should reflect a consensus on what the > advantages and disadvantages are in each case. > > If anything isn't clear (and I suspect it won't be) please let me know. > > Zoe > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
