Plans for b2 in Boost, seeking feeback.

[grafikrobot]

When I moved B2 here my thought on making B2 available in the integrated version Boost uses was to:

1. Do a full B2 release here, i.e. collect current development, test, merge to release branch, tag, etc.
2. Merge that release to the boostorg/build repo develop branch. I did this for the last release already.
3. Wait for any fallout from their CI testing.
4. Merge boostorg/build develop branch to master branch.

The goal is to stabilize Boost usage of B2 to avoid what has previously been an issue of breaking things and dealing with the continuous B2 development. I.e. so that Boost would get as stable B2 versions as practical. At some point it will also be possible to install your own latter B2 release and use it to build Boost ahead of such release syncs.

Does that seems reasonable? Any other ideas?

[Kojoley]

In my opinion development in Boost was already too slow. It usually takes a full release cycle (4 month) to get some changes into the master branch. I needed the #1 patch 2 month ago to simplify my CI, and I am still waiting. Now I even have no idea when I could use that. The long waiting times completely ruins motivation to make changes to external dependencies, and I thought moving B2 out of Boost would release changes faster, but it seems not.

[grafikrobot]

So one aspect that I'm considering is to mirror bfgroup:main changes directly to boostorg:develop. WOuld that alleviate your concerns?

[Kojoley]

Yes, but is not it an opposite of the goal you have described above?