Hi dev's, i would like to ask how we handle the 'stable' flavor. I just recognized that for e.G. base/orogen/interface still is present in stable.
But in the end this is a generic question: 1) when do we allow to 'change' the stable behavior of the packages? 2) for the package-sets itself, when it is allowed to push to stable? 3) when do we remove packages from stable? 3.1) that either not compiling or not wanted to keep anymore (different behavior?) 3.2) We said once that we introduce a "deprecated packages" section but it seems no-one is willing to implement it 4) when do we allow to add packages to stable? Recommendation: As far as i know the next release-candidate will be created from the stable branch, to save the amount of work for each maintainer (specially the release-maintainer) i would recommend the following: 1 & 2) In general changed should be allowed any-time, but following the Pull-request policy for the package-sets 3) since 3.2 is still valid, a removal-announcement on the ML should be sufficient for master, merge the commit which removes something should go in stable after a full-release cycle. 4) as 1) is true, when a dev wants to update/add packages he is free anytime. Thoughts? Matthias -- Dipl.-Inf. Matthias Goldhoorn Space and Underwater Robotic Universität Bremen FB 3 - Mathematik und Informatik AG Robotik Robert-Hooke-Straße 1 28359 Bremen, Germany Zentrale: +49 421 178 45-6611 Besuchsadresse der Nebengeschäftstelle: Robert-Hooke-Straße 5 28359 Bremen, Germany Tel.: +49 421 178 45-4193 Empfang: +49 421 178 45-6600 Fax: +49 421 178 45-4150 E-Mail: [email protected] Weitere Informationen: http://www.informatik.uni-bremen.de/robotik _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
