On Tue, Apr 28, 2015 at 8:18 AM, Janosch Machowinski <[email protected]> wrote: > Hm, > would the deprecation mechanism not > break existing releases ? AFAIK the release > works on the master package set.
Releases will have pinned package sets. Users have the choice to unpin those (for instance if they want to use master packages), but they will have to do it willingly. If the package gets deprecated in master, the only thing the user will have is to force-build the package in his manifest. When the package gets removed from master, that's another story. I would extend the deprecation period to two release cycles for that reason. It would make sure that a package is deprecated in master AND latest-release for one full cycle before it gets removed. Sylvain _______________________________________________ Rock-dev mailing list [email protected] http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
