Tests are run on Boost/develop. To make a new release of Boost, you merge the changes of Boost/develop to Boost/master.
Does that mean that X/develop is not tested?
Yes (and no). It is not integrated into Boost and it is not tested as part of Boost. The same way as the development of zlib is not tested by Debian. Just the releases are integrated and tested.
Why is it needed then?
According to gitflow, this is where the development of X happens. It is also tested of course. On its own, however.
So this basically means that each library has to have its own testing farm, and Boost serves mostly the bundling purpose. A possible solution, I guess, but not sure such approach would be beneficial for the quality of Boost. I doubt that individual developers will be able to do the same amount of testing for their library releases as they had with svn.
how and when are things to be tested: * when a commit is done to someLibrary/develop * when superproject/develop updates the submodule reference to someLibrary/develop? tim