on Sat Aug 24 2013, Daryle Walker <darylew-AT-hotmail.com> wrote:
From: dave@boostpro.com
Boost libraries will be officially developed under Git. People can use bridges or other tools to develop if they like, but Git is going to be a requirement for Boost libraries going forward.
For these questions, I'm talking about a prototype Boost library, kept on a Git repository, a non-Git repository (e.g. Subversion or Mercurial), or winging it on the authors' hard drives. But the first version of a new approved library will be copied over to our GitHub site as a new module without transferring any history (if it was from Git or another SCM)? Daryle W.
The author is free to transfer as much or as little history as he likes. Also, we plan to conduct reviews against a known revision of a GitHub repository, so there will be continuity between the reviewed library and the one that ends up "in Boost." -- Dave Abrahams