Okay, now it's my turn to propose something to sneak into 1.36.0 at the last minute. Fortunately, it's only documentation change. For quite a while, both getting-started, and bjam --help mentioned --toolset option. This in practice, resulted in folks getting wrong analogy and trying to use --variant=debug --link=shared, etc. We agreed (on Boost.Build list), in principle, that we better remove --toolset from documentation, and use 'toolset=' instead -- which has exactly the same effect. So, I would like to commit the following Jamroot change to HEAD and merge to release branch. Any objections? I also would like to see the issue filed against getting-started: http://svn.boost.org/trac/boost/ticket/2050 fixed, and can provide a patch assuming release manager is fine with having this doc tweak merged into release branch, too. Opinions? Thanks, Volodya
Vladimir Prus wrote:
Okay, now it's my turn to propose something to sneak into 1.36.0 at the last minute. Fortunately, it's only documentation change.
For quite a while, both getting-started, and bjam --help mentioned --toolset option. This in practice, resulted in folks getting wrong analogy and trying to use --variant=debug --link=shared, etc. We agreed (on Boost.Build list), in principle, that we better remove --toolset from documentation, and use 'toolset=' instead -- which has exactly the same effect.
So, I would like to commit the following Jamroot change to HEAD and merge to release branch. Any objections?
Go ahead and commit to trunk. You don't need permission from me to do that. But hold off on a branches/release mere commit until enough trunk tests cycle to be sure there are no last minute snafus.
I also would like to see the issue filed against getting-started:
http://svn.boost.org/trac/boost/ticket/2050
fixed, and can provide a patch assuming release manager is fine with having this doc tweak merged into release branch, too.
Opinions?
Docs changes are OK, but don't necessarily expect to see them in the beta. Although I do expect one more cycle of doc builds before the beta goes up on SourceForge. --Beman
Beman Dawes wrote:
Vladimir Prus wrote:
Okay, now it's my turn to propose something to sneak into 1.36.0 at the last minute. Fortunately, it's only documentation change.
For quite a while, both getting-started, and bjam --help mentioned --toolset option. This in practice, resulted in folks getting wrong analogy and trying to use --variant=debug --link=shared, etc. We agreed (on Boost.Build list), in principle, that we better remove --toolset from documentation, and use 'toolset=' instead -- which has exactly the same effect.
So, I would like to commit the following Jamroot change to HEAD and merge to release branch. Any objections?
Go ahead and commit to trunk. You don't need permission from me to do that. But hold off on a branches/release mere commit until enough trunk tests cycle to be sure there are no last minute snafus.
Well, the Jamroot change only changes help message, no behaviour change either. But anyway, as release is not tomorrow, I can wait for test results.
I also would like to see the issue filed against getting-started:
http://svn.boost.org/trac/boost/ticket/2050
fixed, and can provide a patch assuming release manager is fine with having this doc tweak merged into release branch, too.
Opinions?
Docs changes are OK, but don't necessarily expect to see them in the beta. Although I do expect one more cycle of doc builds before the beta goes up on SourceForge.
OK, thanks. - Volodya
participants (3)
-
Beman Dawes -
Vladimir Prus -
Vladimir Prus