As some of you may have noticed, B2 has a new home outside the Boost organization at <https://www.bfgroup.xyz/b2/>. The goal of the move is to elevate B2 development above the constraints of the Boost structure. I.e. to make B2 not just the build system that Boost uses.

The biggest change to make happen is that last week the B2 fork at <https://github.com/bfgroup/b2> became the base git repo of all existing B2 git repos. And hence it means that the git repo <https://github.com/boostorg/build> is now a fork. What does this mean going forward?

This that will not change:

* Boost will still get the build system from the same git repo as it does now.

* The B2 documentation will still be included in the Boost releases.

What will change (eventually), or has already changed:

* Development has moved to the new B2 git repo. And hence PRs for B2 will need to be posted to the new repo.

* The B2 mail list at <https://lists.boost.org/mailman/listinfo.cgi/boost-build> will be replaced by the GitHub discussion forums at <https://github.com/bfgroup/b2/discussions>.

* The B2 version in Boost will be updated from the base git repo for releases of the B2 base only. I.e. a B2 release will get merged to the Boost develop branch. And from there to the master branch.

* The Boost testing of B2 reported at <https://www.boost.org/development/tests/develop/developer/summary.html> will stop showing (and hence running) B2 tests.The testing has already moved to cloud CI. And expanded to cover more platforms than Boost usually tests.

* The B2 web site at <https://boostorg.github.io/build/> will go away.

* The issues at <https://github.com/boostorg/build/issues> will eventually go away (once I deal with enough of them).

--