[1.38.0] beta 2 release candidate
The beta 1 release candidate from earlier in the week had enough issues that I decided not to push it out to sourceforge. Most (all?) of those issues have been corrected, and a new release candidate is up at http://boost.cowic.de/rc/ If no showstoppers surface I plan to move this beta to sourceforge tomorrow (Friday) and announce it here, the users list, and the announce list. The final 1.38.0 release would then come about week later. There are pending bug fixes for Boost.Python and Boost.Asio that are not in the beta but Dave and Chris are planning to have ready for the final release. --Beman
Beman Dawes wrote:
The beta 1 release candidate from earlier in the week had enough issues that I decided not to push it out to sourceforge. Most (all?) of those issues have been corrected, and a new release candidate is up at http://boost.cowic.de/rc/
If no showstoppers surface I plan to move this beta to sourceforge tomorrow (Friday) and announce it here, the users list, and the announce list.
The final 1.38.0 release would then come about week later.
There are pending bug fixes for Boost.Python and Boost.Asio that are not in the beta but Dave and Chris are planning to have ready for the final release.
--Beman _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
No constrained_value?
Hi Neal,
From: Neal Becker No constrained_value?
Well, apart from that there were no official review results yet, I haven't done all the job I am supposed to do before submitting the code because of being quite busy recently. Sorry about the slowliness, I will finalise this as soon as I can. Best regards, Robert
Beman Dawes escribió:
[...]
The final 1.38.0 release would then come about week later.
There are pending bug fixes for Boost.Python and Boost.Asio that are not in the beta but Dave and Chris are planning to have ready for the final release.
I've got a bugfix commited to the trunk for Boost.Flyweight and am waiting for it to cycle through the trunk regression tests. Hopefully toolset steven_watanabe-como, which is the platform of interest here, will have refreshed by Sunday, in which case I wonder wheter I'll be allowed to merge to release on Monday. It's not critical (it only affects Comeau in a noticeable way), so it's OK if I'm denied the permission. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
AMDG joaquin@tid.es wrote:
I've got a bugfix commited to the trunk for Boost.Flyweight and am waiting for it to cycle through the trunk regression tests. Hopefully toolset steven_watanabe-como, which is the platform of interest here, will have refreshed by Sunday, in which case I wonder wheter I'll be allowed to merge to release on Monday.
I'll do an incremental run tonight. In Christ, Steven Watanabe
AMDG joaquin@tid.es wrote:
I've got a bugfix commited to the trunk for Boost.Flyweight and am waiting for it to cycle through the trunk regression tests. Hopefully toolset steven_watanabe-como, which is the platform of interest here, will have refreshed by Sunday, in which case I wonder wheter I'll be allowed to merge to release on Monday. It's not critical (it only affects Comeau in a noticeable way), so it's OK if I'm denied the permission.
Running the flyweight tests manually, the only one that fails is intermodule_holder as of revision 50873. In Christ, Steven Watanabe
________________________________________ De: boost-bounces@lists.boost.org [boost-bounces@lists.boost.org] En nombre de Steven Watanabe [watanabesj@gmail.com] Enviado el: jueves, 29 de enero de 2009 18:04 Para: boost@lists.boost.org Asunto: Re: [boost] [1.38.0] beta 2 release candidate
AMDG
joaquin@tid.es wrote:
I've got a bugfix commited to the trunk for Boost.Flyweight and am waiting for it to cycle through the trunk regression tests. Hopefully toolset steven_watanabe-como, which is the platform of interest here, will have refreshed by Sunday, in which case I wonder wheter I'll be allowed to merge to release on Monday. It's not critical (it only affects Comeau in a noticeable way), so it's OK if I'm denied the permission.
Running the flyweight tests manually, the only one that fails is intermodule_holder as of revision 50873.
So the bugfix works as intended. Thanks for your help! Beman, is it OK to merge to release? Changesets are: https://svn.boost.org/trac/boost/changeset/50828/ https://svn.boost.org/trac/boost/changeset/50829/ Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
On Thu, Jan 29, 2009 at 12:53 PM, JOAQUIN M. LOPEZ MUÑOZ <joaquin@tid.es> wrote:
Running the flyweight tests manually, the only one that fails is intermodule_holder as of revision 50873.
So the bugfix works as intended. Thanks for your help! Beman, is it OK to merge to release? Changesets are:
https://svn.boost.org/trac/boost/changeset/50828/ https://svn.boost.org/trac/boost/changeset/50829/
OK, go ahead. I assume you have already checked tests on other platforms, and they are clear. Thanks, --Beman
On Thu, Jan 29, 2009 at 11:01 AM, <joaquin@tid.es> wrote:
Beman Dawes escribió:
[...]
The final 1.38.0 release would then come about week later.
There are pending bug fixes for Boost.Python and Boost.Asio that are not in the beta but Dave and Chris are planning to have ready for the final release.
I've got a bugfix commited to the trunk for Boost.Flyweight and am waiting for it to cycle through the trunk regression tests. Hopefully toolset steven_watanabe-como, which is the platform of interest here, will have refreshed by Sunday, in which case I wonder wheter I'll be allowed to merge to release on Monday. It's not critical (it only affects Comeau in a noticeable way), so it's OK if I'm denied the permission.
As long as you are sure it isn't affecting other platforms, sure, go ahead once you see trunk test cycles. --Beman
The final 1.38.0 release would then come about week later.
There are pending bug fixes for Boost.Python and Boost.Asio that are not in the beta but Dave and Chris are planning to have ready for the final release.
If it's acceptable there are a couple of inspection report issues that I would like to fix as well for Boost.Math (min/max usage breaks guidelines). John.
On Thu, Jan 29, 2009 at 11:31 AM, John Maddock <john@johnmaddock.co.uk> wrote:
The final 1.38.0 release would then come about week later.
There are pending bug fixes for Boost.Python and Boost.Asio that are not in the beta but Dave and Chris are planning to have ready for the final release.
If it's acceptable there are a couple of inspection report issues that I would like to fix as well for Boost.Math (min/max usage breaks guidelines).
No problem, go ahead. But please be careful not to break anything:-) --Beman
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Thursday, January 29, 2009 4:46 PM Subject: [boost] [1.38.0] beta 2 release candidate
The beta 1 release candidate from earlier in the week had enough issues that I decided not to push it out to sourceforge. Most (all?) of those issues have been corrected, and a new release candidate is up at http://boost.cowic.de/rc/
Hi, In " This release includes new libraries flyweight, swap and scope exit as well as updates to many existing libraries. See Release History for more information." why the Release History link do not points to a file included in the distribution? Currently it is "http://www.boost.org/users/history/version_1_38_0". I understand that this allows to change it without modifying the distribution, but I'm not sure if this is souhaitable, a distribution that do not include itself the release notes sounds a little bit extrange to me. I'm not saying that the page web incuding the release history is not interesting. BTW, how we can go reach for example http://www.boost.org/users/history/version_1_36_0 from http://www.boost.org? Thanks, Vicente
2009/1/29 vicente.botet <vicente.botet@wanadoo.fr>:
I'm not saying that the page web incuding the release history is not interesting. BTW, how we can go reach for example http://www.boost.org/users/history/version_1_36_0 from http://www.boost.org?
If you click on 'Introduction' in the right sidebar, then click on 'Version History' you get a list of old versions, click on the header of a version to get to it's details. I've tried to make it a little easier on the beta site, there's also a link to the version history from the download page (so people can download older versions) and the version history page is hopefully a little easier to use. I'll be putting the new changes live soon-ish (I'm still testing and tweaking things a little). Another simple change I'm thinking of making is adding links to some of the most useful pages to the 'Welcome' part of the sidebar (such as downloads, version history, groups, libraries) so they can be easily found. Daniel
----- Original Message ----- From: "Daniel James" <daniel_james@fmail.co.uk> To: <boost@lists.boost.org> Sent: Thursday, January 29, 2009 10:05 PM Subject: Re: [boost] [1.38.0] beta 2 release candidate
2009/1/29 vicente.botet <vicente.botet@wanadoo.fr>:
I'm not saying that the page web incuding the release history is not interesting. BTW, how we can go reach for example http://www.boost.org/users/history/version_1_36_0 from http://www.boost.org?
If you click on 'Introduction' in the right sidebar, then click on 'Version History' you get a list of old versions, click on the header of a version to get to it's details.
I have followed the links and I finish on a link http://www.boost.org/users/history/#iversion_1_36_0 which is not http://www.boost.org/users/history/version_1_36_0 including only the list of new and modified libraries and no the release note. Version 1.36.0 August 14th, 2008 12:00 GMT New Libraries: Accumulators, Exception, Units, Unordered. Updated Libraries: Asio, Assign, Circular Buffer, Foreach, Function, Hash, Interprocess, Intrusive, Math, Multi-index Containers, MPI, PtrContainer, Spirit, Thread, Wave, Xpressive. Please could you check this? Vicente
2009/1/29 vicente.botet <vicente.botet@wanadoo.fr>:
From: "Daniel James" <daniel_james@fmail.co.uk>
If you click on 'Introduction' in the right sidebar, then click on 'Version History' you get a list of old versions, click on the header of a version to get to it's details.
I have followed the links and I finish on a link http://www.boost.org/users/history/#iversion_1_36_0 which is not http://www.boost.org/users/history/version_1_36_0 including only the list of new and modified libraries and no the release note.
Click on the header and you'll get there. I know this isn't clear, so on the beta site, I've added a 'details' links which will take you to the release notes. Daniel
----- Original Message ----- From: "Daniel James" <daniel_james@fmail.co.uk> To: <boost@lists.boost.org> Sent: Thursday, January 29, 2009 10:23 PM Subject: Re: [boost] [1.38.0] beta 2 release candidate
2009/1/29 vicente.botet <vicente.botet@wanadoo.fr>:
From: "Daniel James" <daniel_james@fmail.co.uk>
If you click on 'Introduction' in the right sidebar, then click on 'Version History' you get a list of old versions, click on the header of a version to get to it's details.
I have followed the links and I finish on a link http://www.boost.org/users/history/#iversion_1_36_0 which is not http://www.boost.org/users/history/version_1_36_0 including only the list of new and modified libraries and no the release note.
Click on the header and you'll get there. I know this isn't clear, so on the beta site, I've added a 'details' links which will take you to the release notes.
Ok, I see now. Yes it will be better to make more evident that there is a link there. Vicente
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Thursday, January 29, 2009 4:46 PM Subject: [boost] [1.38.0] beta 2 release candidate
The beta 1 release candidate from earlier in the week had enough issues that I decided not to push it out to sourceforge. Most (all?) of those issues have been corrected, and a new release candidate is up at http://boost.cowic.de/rc/
Hi, In a preceding post you said From: "Beman Dawes" <bdawes@acm.org>
On Tue, Jan 27, 2009 at 2:09 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
1. The page http://beta.boost.org/doc/libs/ allowing to show some Boost library has not been merged. Merged.
How can we get this page on the beta2 distribution? Thanks, Vicente
2009/1/29 vicente.botet <vicente.botet@wanadoo.fr>:
From: "Beman Dawes" <bdawes@acm.org>
On Tue, Jan 27, 2009 at 2:09 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
1. The page http://beta.boost.org/doc/libs/ allowing to show some Boost library has not been merged. Merged.
How can we get this page on the beta2 distribution?
I'm not sure exactly what you mean, the library list in the distribution is at 'libs/libraries.htm' and is linked to from most pages in the distribution. If you want to get the library documentation on the web, someone with ftp access has to add upload it to the website (I don't have ftp access). Then a few changes will need to be made to the site so that it'll display beta documentation. In the past, we've only uploaded the final release to the site. Daniel
----- Original Message ----- From: "Daniel James" <daniel_james@fmail.co.uk> To: <boost@lists.boost.org> Sent: Thursday, January 29, 2009 10:09 PM Subject: Re: [boost] [1.38.0] beta 2 release candidate
2009/1/29 vicente.botet <vicente.botet@wanadoo.fr>:
From: "Beman Dawes" <bdawes@acm.org>
On Tue, Jan 27, 2009 at 2:09 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
1. The page http://beta.boost.org/doc/libs/ allowing to show some Boost library has not been merged. Merged.
How can we get this page on the beta2 distribution?
I'm not sure exactly what you mean, the library list in the distribution is at 'libs/libraries.htm' and is linked to from most pages in the distribution. If you want to get the library documentation on the web, someone with ftp access has to add upload it to the website (I don't have ftp access). Then a few changes will need to be made to the site so that it'll display beta documentation. In the past, we've only uploaded the final release to the site.
Well, I think that this has been discused already. A lot of people prefer the fonctianalities provided by this page http://beta.boost.org/doc/libs/ compared to 'libs/libraries.htm' in the distribution because it is a superset. I don't kwno which technology use this page. Is there a technical issue to dont include this kind of pages on the distribution? Vicente Vicente
On Thu, Jan 29, 2009 at 4:34 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
Well, I think that this has been discused already. A lot of people prefer the fonctianalities provided by this page http://beta.boost.org/doc/libs/ compared to 'libs/libraries.htm' in the distribution because it is a superset. I don't kwno which technology use this page. Is there a technical issue to dont include this kind of pages on the distribution?
Not that it matters this late in the game (or at all?), but I prefer the former page. The libs/libraries.htm page really has some usability issues. Having all of the Summaries, Author, Release Date, etc always visible makes scrolling through the list extremely tedious. Not to mention the fact that the Alphabetical option doesn't even sort correctly. --Michael Fawcett
----- Original Message ----- From: "Michael Fawcett" <michael.fawcett@gmail.com> To: <boost@lists.boost.org> Sent: Thursday, January 29, 2009 10:42 PM Subject: Re: [boost] [1.38.0] beta 2 release candidate
On Thu, Jan 29, 2009 at 4:34 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
Well, I think that this has been discused already. A lot of people prefer the fonctianalities provided by this page http://beta.boost.org/doc/libs/ compared to 'libs/libraries.htm' in the distribution because it is a superset. I don't kwno which technology use this page. Is there a technical issue to dont include this kind of pages on the distribution?
Not that it matters this late in the game (or at all?), but I prefer the former page.
The libs/libraries.htm page really has some usability issues. Having all of the Summaries, Author, Release Date, etc always visible makes scrolling through the list extremely tedious. Not to mention the fact that the Alphabetical option doesn't even sort correctly.
Hi, you are right. The advantage of the view http://beta.boost.org/doc/libs/ is that we can add multiple view. Maybe a summarized view could be added (something like in Categorized but without the categories). What about adding Sorted By Author page? Please could you signal the Alphabetical error? Thanks, Vicente
----- Original Message ----- From: "Michael Fawcett" <michael.fawcett@gmail.com> To: <boost@lists.boost.org> Sent: Friday, January 30, 2009 12:01 AM Subject: Re: [boost] [1.38.0] beta 2 release candidate
On Thu, Jan 29, 2009 at 5:53 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
Please could you signal the Alphabetical error?
Libraries out of order:
CRC GIL IO State Savers MPI MPL TR1 uBLAS
Are you sure we are looking the same page http://beta.boost.org/doc/libs/? Vicente
2009/1/29 vicente.botet <vicente.botet@wanadoo.fr>:
Are you sure we are looking the same page http://beta.boost.org/doc/libs/?
I fixed that page on the beta site after reading Michael's first email. The ordering was case sensitive before which is why those libraries were in the wrong place. Daniel
AMDG Michael Fawcett wrote:
On Thu, Jan 29, 2009 at 5:53 PM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
Please could you signal the Alphabetical error?
Libraries out of order:
CRC GIL IO State Savers MPI MPL TR1 uBLAS
In other words, the sort is case sensitive. In Christ, Steven Watanabe
On Thu, Jan 29, 2009 at 9:38 PM, Steven Watanabe <watanabesj@gmail.com> wrote:
In other words, the sort is case sensitive.
Yes, I gathered that ;) The older libs page wasn't sorted that way, and humans don't tend to care. BTW, uBLAS was listed last. How, in any type of sorting, does lower-case u come after capital W? --Michael Fawcett
2009/2/1 Michael Fawcett <michael.fawcett@gmail.com>:
On Thu, Jan 29, 2009 at 9:38 PM, Steven Watanabe <watanabesj@gmail.com> wrote:
In other words, the sort is case sensitive.
Yes, I gathered that ;)
The older libs page wasn't sorted that way, and humans don't tend to care.
BTW, uBLAS was listed last. How, in any type of sorting, does lower-case u come after capital W?
Because lower case letters come after upper case in ASCII.
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Thursday, January 29, 2009 4:46 PM Subject: [boost] [1.38.0] beta 2 release candidate
The beta 1 release candidate from earlier in the week had enough issues that I decided not to push it out to sourceforge. Most (all?) of those issues have been corrected, and a new release candidate is up at http://boost.cowic.de/rc/
If no showstoppers surface I plan to move this beta to sourceforge tomorrow (Friday) and announce it here, the users list, and the announce list.
Is it a showstoppers that not all updates have been included in the Release note? Or as the Release note is not included at all on the distribution this not an issue at all? Vicente
participants (10)
-
Beman Dawes -
Daniel James -
JOAQUIN M. LOPEZ MUÑOZ -
joaquin＠tid.es
-
John Maddock -
Michael Fawcett -
Neal Becker -
Robert Kawulak -
Steven Watanabe -
vicente.botet