Oliver Kowalke wrote
Do we have any policies about leaving trunk broken.
In the case of Context, no-one uses it yet, but for anything that someone depends on, breaking trunk for it breaks people that for some reason uses trunk.
what about evolution of the code/interface?
boost-docu states: "Library Maintainer's Rights and Responsibilities: You are free to change your library in any way you wish, and you are encouraged to actively make improvements."
The modification I've done was a request from one of the reviewers of boost.context.
You can always try be backward compatible. E.g. preserve the existing files, which could include the new ones. Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/context-Trying-to-compile-Coroutine-on-tr... Sent from the Boost - Dev mailing list archive at Nabble.com.