[1.38.0] beta release candidate
[1.38.0] beta release candidate packages are available at http://boost.cowic.de/rc/ I'm doing a library build right now on Windows/VC++ 9.0. I'd appreciate it if someone could try a library build on a Linux system, and report any problems. Although we won't hold the beta for minor tweaks, I would like to be sure that docs are present and libraries build before pushing this out to SourceForge. Thanks, --Beman
Hi, Just some issues: 1. The page http://beta.boost.org/doc/libs/ allowing to show some Boost library has not been merged. 2. The documentation for the new scoped_exit library is not included yet 3. The release is missing The page https://svn.boost.org/trac/boost/browser/website/public_html/beta/feed/histo... contains already some items, but not all. Between the library that have been modified some of them contains already an history on its documentation. For these we should at least add an item with "For more detail, see the [@ ... * DateTime Changes from Boost 1.34 to 1.38 (date_time 1.05 to 1.06) * Interprocess Boost 1.38 Release * Intrusive Boost 1.38 Release * MultiIndex Boost 1.38 release * RegEx Boost 1.38 Is there a systematic way to know which libraries have made some changes? Best, Vicente
On Tue, Jan 27, 2009 at 2:09 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
Hi,
Just some issues:
1. The page http://beta.boost.org/doc/libs/ allowing to show some Boost library has not been merged.
Merged.
2. The documentation for the new scoped_exit library is not included yet
Hummm... The docs aren't in trunk either:-( Alexander, what's the status of the docs?
3. The release is missing The page https://svn.boost.org/trac/boost/browser/website/public_html/beta/feed/histo... contains already some items, but not all.
Between the library that have been modified some of them contains already an history on its documentation. For these we should at least add an item with "For more detail, see the [@ ...
* DateTime Changes from Boost 1.34 to 1.38 (date_time 1.05 to 1.06) * Interprocess Boost 1.38 Release * Intrusive Boost 1.38 Release * MultiIndex Boost 1.38 release * RegEx Boost 1.38
Is there a systematic way to know which libraries have made some changes?
I'm sure it is possible to get a raw list out of subversion, and perhaps if it was filtered by file extension you could identify the libraries with actual code changes. Thanks, --Beman
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: <boost@lists.boost.org> Sent: Tuesday, January 27, 2009 9:54 PM Subject: Re: [boost] [1.38.0] beta release candidate
On Tue, Jan 27, 2009 at 2:09 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
2. The documentation for the new scoped_exit library is not included yet
Hummm... The docs aren't in trunk either:-( Alexander, what's the status of the docs?
I see a qbk file on the doc directory. Vicente
On Tue, Jan 27, 2009 at 4:20 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: <boost@lists.boost.org> Sent: Tuesday, January 27, 2009 9:54 PM Subject: Re: [boost] [1.38.0] beta release candidate
On Tue, Jan 27, 2009 at 2:09 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
2. The documentation for the new scoped_exit library is not included yet
Hummm... The docs aren't in trunk either:-( Alexander, what's the status of the docs?
I see a qbk file on the doc directory.
You're right. I was looking at an out-of-date working copy. So it looks like a documentation integration issue. Daniel? Did I jump the gun on something you are working on? --Beman
2009/1/27 Beman Dawes <bdawes@acm.org>:
On Tue, Jan 27, 2009 at 4:20 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
I see a qbk file on the doc directory.
You're right. I was looking at an out-of-date working copy.
So it looks like a documentation integration issue.
Daniel? Did I jump the gun on something you are working on?
No, I've only just found out that scope exit is in release. I'll try to get everything sorted out by tomorrow. Daniel
On Tue, Jan 27, 2009 at 5:03 PM, Daniel James <daniel_james@fmail.co.uk> wrote:
2009/1/27 Beman Dawes <bdawes@acm.org>:
On Tue, Jan 27, 2009 at 4:20 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
I see a qbk file on the doc directory.
You're right. I was looking at an out-of-date working copy.
So it looks like a documentation integration issue.
Daniel? Did I jump the gun on something you are working on?
No, I've only just found out that scope exit is in release. I'll try to get everything sorted out by tomorrow.
No problem. Thanks for working on this! --Beman
Daniel James <daniel_james <at> fmail.co.uk> writes:
No, I've only just found out that scope exit is in release. I'll try to get everything sorted out by tomorrow.
Daniel, That's right, after an unsuccessful attempt to run bjam in the ./doc directory I copied all documentation from trunk to release hoping it would magically work. But it does not work. Thanks for doing this. Alex
2009/1/27 vicente.botet <vicente.botet@wanadoo.fr>:
1. The page http://beta.boost.org/doc/libs/ allowing to show some Boost library has not been merged.
Sorry, I'm unlikely to develop anything new for the website soon, as my priority has to be documenting the documentation tools (which is well overdue). I don't think we have anything which tracks when a library is merged to release. The best source of information is the review schedule page, but that only tracks when a library is added to trunk, and when it's released. And I don't think how up to date it is. http://www.boost.org/community/review_schedule.html
2. The documentation for the new scoped_exit library is not included yet
Thanks, I didn't realise it was in the release branch, I'm working on it.
3. The release is missing The page https://svn.boost.org/trac/boost/browser/website/public_html/beta/feed/histo... contains already some items, but not all.
Yep, it's not finished.
Between the library that have been modified some of them contains already an history on its documentation. For these we should at least add an item with "For more detail, see the [@ ...
* DateTime Changes from Boost 1.34 to 1.38 (date_time 1.05 to 1.06) * Interprocess Boost 1.38 Release * Intrusive Boost 1.38 Release * MultiIndex Boost 1.38 release * RegEx Boost 1.38
That's up to the library authors. Although, I suppose we could store a list of changelogs somewhere, which I could use to start the release notes.
Is there a systematic way to know which libraries have made some changes?
It takes a bit work to interpret the output: svn diff --summarize http://svn.boost.org/svn/boost/tags/release/Boost_1_37_0 http://svn.boost.org/svn/boost/branches/release There are quite a lot of irrelevant changes - for example I fixed a lot of subversion file properties, which isn't really worth noting. Daniel Daniel
Hi, I manage to compile the full beta on Linux (64 bits gcc 4.3.2). Some minor comments on the docs: in boost_1_38_0_beta1/index.html:
Changes in this release This release includes ??? new libraries new libraries is not updated yet.
in boost_1_38_0_beta1/libs/libraries.htm#Alphabetically
flyweight - Design pattern to manage larque quantities s/larque/large
Dirk On Tue, Jan 27, 2009 at 4:54 PM, Beman Dawes <bdawes@acm.org> wrote:
[1.38.0] beta release candidate packages are available at http://boost.cowic.de/rc/
I'm doing a library build right now on Windows/VC++ 9.0.
I'd appreciate it if someone could try a library build on a Linux system, and report any problems.
Although we won't hold the beta for minor tweaks, I would like to be sure that docs are present and libraries build before pushing this out to SourceForge.
Thanks,
--Beman _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Tue, Jan 27, 2009 at 2:15 PM, Dirk Moermans <dirkmoermans@gmail.com> wrote:
Hi,
I manage to compile the full beta on Linux (64 bits gcc 4.3.2).
Great! Thanks!
Some minor comments on the docs:
in boost_1_38_0_beta1/index.html:
Changes in this release This release includes ??? new libraries new libraries is not updated yet.
Fixed and merged.
in boost_1_38_0_beta1/libs/libraries.htm#Alphabetically
flyweight - Design pattern to manage larque quantities s/larque/large
Fixed in two places and merged. Thanks! --Beman
on Tue Jan 27 2009, Beman Dawes <bdawes-AT-acm.org> wrote:
[1.38.0] beta release candidate packages are available at http://boost.cowic.de/rc/
I'm doing a library build right now on Windows/VC++ 9.0.
I'd appreciate it if someone could try a library build on a Linux system, and report any problems.
Although we won't hold the beta for minor tweaks, I would like to be sure that docs are present and libraries build before pushing this out to SourceForge.
Hi Beman, There were bugs discovered last week in Boost.Parameter for which I have checked in fixes to trunk. Can they be merged to release? Thanks, -- Dave Abrahams BoostPro Computing http://www.boostpro.com
On Tue, Jan 27, 2009 at 2:33 PM, David Abrahams <dave@boostpro.com> wrote:
on Tue Jan 27 2009, Beman Dawes <bdawes-AT-acm.org> wrote:
[1.38.0] beta release candidate packages are available at http://boost.cowic.de/rc/
I'm doing a library build right now on Windows/VC++ 9.0.
I'd appreciate it if someone could try a library build on a Linux system, and report any problems.
Although we won't hold the beta for minor tweaks, I would like to be sure that docs are present and libraries build before pushing this out to SourceForge.
Hi Beman,
There were bugs discovered last week in Boost.Parameter for which I have checked in fixes to trunk. Can they be merged to release?
Yes, assuming they are stable on trunk. --Beman
On Tue, Jan 27, 2009 at 2:35 PM, Remko Tronçon <remko@el-tramo.be> wrote:
I'd appreciate it if someone could try a library build on a Linux system, and report any problems.
Although you didn't ask
Sorry; I should have been more inclusive.
: I managed to build & install boost on darwin/ppc.
Great! Thanks! --Beman
participants (7)
-
Alexander Nasonov -
Beman Dawes -
Daniel James -
David Abrahams -
Dirk Moermans -
Remko Tronçon -
vicente.botet