2012/10/16 Alessandro Adamou <[email protected]>: > Hi, > > I have a question on the release policy. > > The criterion for releasing a standalone module is that it has to be working > on the latest launcher released (the 0.9.0-incubating one iirc)? Or can we > assume it to be working on a compiled launcher from a certain more recent > trunk revision?
Releasing components and launcher configurations are two separate things. We should aim for releasing a stable launcher configuration that only includes released components. That is the plan for the stable launcher. This launcher is supposed to use only released components. At the moment we are missing correct releases of bundlelist that would enable us to create such a stable launcher. At the moment it is just fine if everything is working in the SNAPSHOT full launcher. We do not have any other criteria, yet. > If so should/can we release up-to-date dependencies along with the module > itself or call for separate releases? When releasing a component all of its SNAPSHOT dependencies have to be released. If your component has dependencies e.g. to commons components, then those need to be released as well. We can call a vote for a component release that includes releases of commons components. I would just like to separate releases of the main components, i.e. entityhub, contenthub, enhancer, ontologymanager. Best, - Fabian
