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?
If so should/can we release up-to-date dependencies along with the module itself or call for separate releases?
Thanks Alessandro On 10/11/12 11:10 PM, Fabian Christ wrote:
Hi, I am investigating the components that should go for a release in the near future. We should try to bring as much components to a 1.0 status as possible. After graduation it would be a good sign to start and establish a release cycle. My first release candidate would be the Enhancer with all Enhancement Engines. So I will check the Enhancer and engines if all requirements for a release are met (license, POMs, etc). What about other components? Please, make suggestions as I do not have a detailed overview of the status of all the code parts and branches. Best, - Fabian
-- M.Sc. Alessandro Adamou Alma Mater Studiorum - Università di Bologna Department of Computer Science Mura Anteo Zamboni 7, 40127 Bologna - Italy Semantic Technology Laboratory (STLab) Institute for Cognitive Science and Technology (ISTC) National Research Council (CNR) Via Nomentana 56, 00161 Rome - Italy "I will give you everything, just don't demand anything." (Ettore Petrolini, 1917) Not sent from my iSnobTechDevice
