According to: http://www.boost.org/development/index.html we're supposed to have beta release tomorrow, and final release on 31st. Are doc changes allowed in between? What becomes apparent on IRC, is that the current install docs have issues: - Boost.Build command line syntax docs are not very good, because they split information across several pages - Getting started fails to refer to command line syntax directly. - Getting started lists various variants that may be built, and their names, but does not give Boost.Build options to request those variants, so people start to improvise various interesting syntaxes. - It fails to clearly say that 'configure'/'make' is the approach that's only good for native, all-default build. I think it would be good to clear this up, and can work on this, but of course only if the changes can be gotten in. Comments? - Volodya
Vladimir Prus wrote:
According to:
http://www.boost.org/development/index.html
we're supposed to have beta release tomorrow, and final release on 31st.
Did I misunderstand that the target date has been shifted to Monday, because the weekend is when many (most?) people have time to devote? -- Genny
Vladimir Prus wrote:
According to:
http://www.boost.org/development/index.html
we're supposed to have beta release tomorrow, and final release on 31st. Are doc changes allowed in between?
What becomes apparent on IRC, is that the current install docs have issues:
- Boost.Build command line syntax docs are not very good, because they split information across several pages - Getting started fails to refer to command line syntax directly. - Getting started lists various variants that may be built, and their names, but does not give Boost.Build options to request those variants, so people start to improvise various interesting syntaxes. - It fails to clearly say that 'configure'/'make' is the approach that's only good for native, all-default build.
I think it would be good to clear this up, and can work on this, but of course only if the changes can be gotten in. Comments?
I would be OK with this. In fact, more than OK, because I also have doc changes I'd like to get in. :-P But I recuse myself and will let Beman make the final decision on whether doc changes are allowed after the beta. -- Eric Niebler BoostPro Computing http://www.boostpro.com
Eric Niebler wrote:
I would be OK with this. In fact, more than OK, because I also have doc changes I'd like to get in. :-P But I recuse myself and will let Beman make the final decision on whether doc changes are allowed after the beta.
I think it depends on what Boost wants from a beta. It isn't completely fair to just leave the decision to Beman. -- Genny
On Thu, Oct 16, 2008 at 2:10 PM, Eric Niebler <eric@boost-consulting.com>wrote:
Vladimir Prus wrote:
According to:
http://www.boost.org/development/index.html
we're supposed to have beta release tomorrow, and final release on 31st. Are doc changes allowed in between?
What becomes apparent on IRC, is that the current install docs have issues:
- Boost.Build command line syntax docs are not very good, because they split information across several pages - Getting started fails to refer to command line syntax directly. - Getting started lists various variants that may be built, and their names, but does not give Boost.Build options to request those variants, so people start to improvise various interesting syntaxes. - It fails to clearly say that 'configure'/'make' is the approach that's only good for native, all-default build.
I think it would be good to clear this up, and can work on this, but of course only if the changes can be gotten in. Comments?
I would be OK with this. In fact, more than OK, because I also have doc changes I'd like to get in. :-P But I recuse myself and will let Beman make the final decision on whether doc changes are allowed after the beta.
Yes to anyone with document updates. And I did push the beta date out until Monday. Thanks, --Beman
participants (4)
-
Beman Dawes -
Eric Niebler -
Gennaro Prota -
Vladimir Prus