Boost 1.61.0 Beta 1
The first beta packages for 1.61.0 beta 1 are now available: http://boost.cowic.de/rc/boost_1_61_0_b1.zip http://boost.cowic.de/rc/boost_1_61_0_b1.7z http://boost.cowic.de/rc/boost_1_61_0_b1.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_b1.tar.gz There are no changes compared to RC2, expect for different names of the archives and different name of the top-level directory in the archives. The SHA256 checksums are as follows: 3f8888099ee6f62b412a13be916dead2bacbdd6d69e5afd5b6fea4bb738e5df4 boost_1_61_0_b1.7z 866941f0038b27fcc69ced1490b2dc5fa8d20f505d66b939a92a68ef194d1a6c boost_1_61_0_b1.tar.bz2 0b92c5fb5b91641409b9675b2fd11d3b3fa5f71dd986d3b5fb03da201bf55474 boost_1_61_0_b1.tar.gz 9dffe5ee7f5f7bf7695f5738c686e44bd266933e3ca68732b0de5520c3c82615 boost_1_61_0_b1.zip Signed list of checksums should be posted within 24 hours. As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. It was discovered that the .zip and .7z archives actually have LF line endings, at least in some places. Fixing this is not quite trivial, as Travis uses ancient version of Ubuntu and Git, and is not deemed critical, as most Windows editors handle LF just fine. We might do something for the final release, or might not. Thanks! -- The release managers
On Thu, Mar 31, 2016 at 3:05 AM, Vladimir Prus
The first beta packages for 1.61.0 beta 1 are now available: <snip>
It was discovered that the .zip and .7z archives actually have LF line endings, at least in some places. Fixing this is not quite trivial, as Travis uses ancient version of Ubuntu and Git, and is not deemed critical, as most Windows editors handle LF just fine. We might do something for the final release, or might not.
I would vote for leaving it, I've always thought it would be preferable if all the releases were the same. I think notepad.exe is the only app that still has issues with line endings, though I'd be interested in hearing some history on why was different for the windows releases. Tom
On Thu, Mar 31, 2016 at 3:05 AM, Vladimir Prus
The first beta packages for 1.61.0 beta 1 are now available:
http://boost.cowic.de/rc/boost_1_61_0_b1.zip http://boost.cowic.de/rc/boost_1_61_0_b1.7z http://boost.cowic.de/rc/boost_1_61_0_b1.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_b1.tar.gz
There are no changes compared to RC2, expect for different names of the archives and different name of the top-level directory in the archives.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the windows binaries for this beta to sourceforge. They can be found at: https://sourceforge.net/projects/boost/files/boost-binaries/1.61.0_b1 Below are the SHA-256 hashes for the archives. This e-mail is signed with my GPG key. Tom fd76a36eb135e7d64a5b489d562f88090d41d8e0594e13e70908acd8960e44a6 boost_1_61_0_b1-32bitlog.txt 64262055ab7da9740a35a1fbd7d7b63305e92a307b8292c02ee6fe37e47ed7c1 boost_1_61_0_b1-64bitlog.txt 56448b715c448e1a8ed4b2cfb1d3f4c29cfb8f010d9fabd6d3ae3ec84622d734 boost_1_61_0_b1-bin-msvc-all-32-64.7z b27fffa804bf816d72effeda9daab0bd1d1f92879bd9f0db2d032b1101e72609 boost_1_61_0_b1-msvc-10.0-32.exe 236bf1d40f7d733122fec60ed91cbdc0305470b1d5a2ff0bcde689d8784355cd boost_1_61_0_b1-msvc-10.0-64.exe 413efaab0d551c2913eff00a11ce84094841b2928ab45a0c89fa82ccdf54ee3f boost_1_61_0_b1-msvc-11.0-32.exe f55e4264416f2b63646d1c8dcb5ac7aa9aa3ec7621c526f35fc0c62d9b45336a boost_1_61_0_b1-msvc-11.0-64.exe de11cc0a55ffd91c4f538d0b5e3ebec28e542c41ee26d549e20e5c0b1c945ba4 boost_1_61_0_b1-msvc-12.0-32.exe 4b7ced15f1564437503cc4767c46b8e19ba746a41a26abdc1299f9314c73270f boost_1_61_0_b1-msvc-12.0-64.exe d32ee0ed3ea4a7a66e8d0eec182ae2d8ab83ff06bb57492e3d99b6f075e4c15f boost_1_61_0_b1-msvc-14.0-32.exe 961eb5f4a6ee71dfd02652858f99bdcf470ddb3049cb00d2172659c984f21b87 boost_1_61_0_b1-msvc-14.0-64.exe acf8292a870d267ab319d7e421445fbbd188c5a416050c1d03b1d680a6f6915b boost_1_61_0_b1-msvc-8.0-32.exe 3b94dac0b00e40f754e7ee828212caec73b8cdcc09d545705a923fefe50b2ca2 boost_1_61_0_b1-msvc-8.0-64.exe 461f38bfea6c0a3e1a904bb014877157d475ef502ec5f4fb1ba8d2c95dee64d7 boost_1_61_0_b1-msvc-9.0-32.exe 4e33f383cb80d259c1deff2eb70e15faf9d1f9014f62fcfff72cc31b1662d06e boost_1_61_0_b1-msvc-9.0-64.exe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJW/RTaAAoJEO5CwwL7YZSo0GoP/0OY/GDD3z0rIqamnxCzTMLu qe9dtd7DaG6U0X7TYyNK6geS352qemxJ5LbkAVmrVWTr9OdGhVApkA862suU7orL SIY94dz1AYL6edgQ7TRAu/0t+h7aj/bI3LCSZPpx3Ef0AnxEUnfGSr6gbSTYOXG2 o0HGORadVJj5EHkuv8w+tf8Oplw3fvPhkQ6XXb1Yc57kWviphzAMaFTnA+uhnMJN yWp0lGVo4XtJvQdMe5vO8H5I/tePMmNhjV5/tQK7U3qoHrkCArobgTcfaWUiUbXq wbLFFLmXnlngdavb88/OoTfL/lsqN9jQzDM/HJ7EYVbqbpW6y0LOye6AvzusbVEA nyPncxChhmxzJ0G8zCQuks4sL9COMPucnLGsa8CSfbKPo4Pw0+mTpnRVtkaXUjvI CC3tBGpoIX/xX+8VuSdIqnRjDd99kW/x6NfsjnHbhDg14HMXIA3vRt3jjFQcjUGI snj/uYiR/uuDrhQpjt+bUFO1UCjVO1/YF2QKGfitFgAzVfyO1+8VdTRwvTJMf3Ra NsPjDdYVgezhWSUThORknAreGW1u8JHlfwJx864O26g+OJ/jepjbi4PhETuL4nFZ YKmalmCVM7Ty1cNhrwIRmGTP02085uLOZNjb+z+pknrcTJO0q2UbaiAylH5PmrXc d1Uxw3GsIzPu3b4HxmV5 =Cpp+ -----END PGP SIGNATURE-----
On 03/31/2016 11:05 AM, Vladimir Prus wrote:
The first beta packages for 1.61.0 beta 1 are now available:
http://boost.cowic.de/rc/boost_1_61_0_b1.zip http://boost.cowic.de/rc/boost_1_61_0_b1.7z http://boost.cowic.de/rc/boost_1_61_0_b1.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_b1.tar.gz
There are no changes compared to RC2, expect for different names of the archives and different name of the top-level directory in the archives.
The SHA256 checksums are as follows:
3f8888099ee6f62b412a13be916dead2bacbdd6d69e5afd5b6fea4bb738e5df4 boost_1_61_0_b1.7z 866941f0038b27fcc69ced1490b2dc5fa8d20f505d66b939a92a68ef194d1a6c boost_1_61_0_b1.tar.bz2 0b92c5fb5b91641409b9675b2fd11d3b3fa5f71dd986d3b5fb03da201bf55474 boost_1_61_0_b1.tar.gz 9dffe5ee7f5f7bf7695f5738c686e44bd266933e3ca68732b0de5520c3c82615 boost_1_61_0_b1.zip
Signed list of checksums should be posted within 24 hours.
Attached is the signed list of signatures. The GPG key can be found at: https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4 or https://vladimirprus.com/vladimir.prus.gpg The key fingerprint is: C5F0 F367 AA66 616F B839 806E DA47 2E86 5975 3BA4 -- Vladimir Prus http://vladimirprus.com
On Thu, Mar 31, 2016 at 4:00 PM, Vladimir Prus
On 03/31/2016 11:05 AM, Vladimir Prus wrote:
The first beta packages for 1.61.0 beta 1 are now available:
http://boost.cowic.de/rc/boost_1_61_0_b1.zip http://boost.cowic.de/rc/boost_1_61_0_b1.7z http://boost.cowic.de/rc/boost_1_61_0_b1.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_b1.tar.gz
Is this beta going to go up to sourceforge? That is the normal process, right? Tom
On Thu, Mar 31, 2016 at 4:22 PM, Tom Kent
On Thu, Mar 31, 2016 at 4:00 PM, Vladimir Prus
wrote: On 03/31/2016 11:05 AM, Vladimir Prus wrote:
The first beta packages for 1.61.0 beta 1 are now available:
http://boost.cowic.de/rc/boost_1_61_0_b1.zip http://boost.cowic.de/rc/boost_1_61_0_b1.7z http://boost.cowic.de/rc/boost_1_61_0_b1.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_b1.tar.gz
Is this beta going to go up to sourceforge? That is the normal process, right?
Ping?
On 5 April 2016 at 02:36, Tom Kent
On Thu, Mar 31, 2016 at 4:22 PM, Tom Kent
wrote: Is this beta going to go up to sourceforge? That is the normal process, right?
Ping?
We're trying another hosting service. I added links to the website yesterday, sorry that was a bit slow. https://bintray.com/boostorg/release/boost/1.61.0.beta.1/view
On Tue, Apr 5, 2016 at 2:46 AM, Daniel James
On 5 April 2016 at 02:36, Tom Kent
wrote: On Thu, Mar 31, 2016 at 4:22 PM, Tom Kent
wrote: Is this beta going to go up to sourceforge? That is the normal process, right?
Ping?
We're trying another hosting service. I added links to the website yesterday, sorry that was a bit slow.
https://bintray.com/boostorg/release/boost/1.61.0.beta.1/view
Can we put the windows binary builds up there as well? I had already uploaded them to sourceforge since no one told me the process had changed. Tom
On Tue, Apr 5, 2016 at 7:28 AM, Tom Kent
On Tue, Apr 5, 2016 at 2:46 AM, Daniel James
wrote: On Thu, Mar 31, 2016 at 4:22 PM, Tom Kent
wrote: Is this beta going to go up to sourceforge? That is the normal
On 5 April 2016 at 02:36, Tom Kent
wrote: process, right?
Ping?
We're trying another hosting service. I added links to the website yesterday, sorry that was a bit slow.
https://bintray.com/boostorg/release/boost/1.61.0.beta.1/view
Can we put the windows binary builds up there as well? I had already uploaded them to sourceforge since no one told me the process had changed.
Sure.. Can you go here https://bintray.com/boostorg and hit the join button near the top. So I can give you access to upload the binaries. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On Tue, Apr 5, 2016 at 8:51 AM, Rene Rivera
On Tue, Apr 5, 2016 at 7:28 AM, Tom Kent
wrote: On Tue, Apr 5, 2016 at 2:46 AM, Daniel James
wrote: On Thu, Mar 31, 2016 at 4:22 PM, Tom Kent
wrote: Is this beta going to go up to sourceforge? That is the normal
On 5 April 2016 at 02:36, Tom Kent
wrote: process, right?
Ping?
We're trying another hosting service. I added links to the website yesterday, sorry that was a bit slow.
https://bintray.com/boostorg/release/boost/1.61.0.beta.1/view
Can we put the windows binary builds up there as well? I had already uploaded them to sourceforge since no one told me the process had changed.
Sure.. Can you go here https://bintray.com/boostorg and hit the join button near the top. So I can give you access to upload the binaries.
Well that was a bust. They don't allow files > 250MB on the site. Several of the windows packages are bigger than that. I vote that we go back to sourceforge for our primary download site, they don't have problems like this. They've also been doing a pretty good job at cleaning up their reputation over the last few weeks. If we want to support two sites one for the source and one for the binaries, I don't think that's the end of the world, but I don't see it as ideal. Either way, can we also upload the source releases there even if it isn't the primary place to go? There are lots of links all over the internet that are pointing people there for downloads of boost, it would be sad if people following those only saw the old versions. Tom
On Tue, Apr 5, 2016 at 9:21 PM, Tom Kent
Either way, can we also upload the source releases there even if it isn't the primary place to go? There are lots of links all over the internet that are pointing people there for downloads of boost, it would be sad if people following those only saw the old versions.
It might be fine if they saw just a README which conveyed that the new source releases are now available on bintray.com/boostorg. Glen
On Tue, Apr 5, 2016 at 8:21 PM, Tom Kent
On Tue, Apr 5, 2016 at 8:51 AM, Rene Rivera
wrote: On Tue, Apr 5, 2016 at 7:28 AM, Tom Kent
wrote: On Tue, Apr 5, 2016 at 2:46 AM, Daniel James
wrote: On Thu, Mar 31, 2016 at 4:22 PM, Tom Kent
wrote: > Is this beta going to go up to sourceforge? That is the normal
On 5 April 2016 at 02:36, Tom Kent
wrote: process, right?
Ping?
We're trying another hosting service. I added links to the website yesterday, sorry that was a bit slow.
https://bintray.com/boostorg/release/boost/1.61.0.beta.1/view
Can we put the windows binary builds up there as well? I had already uploaded them to sourceforge since no one told me the process had changed.
Sure.. Can you go here https://bintray.com/boostorg and hit the join button near the top. So I can give you access to upload the binaries.
Well that was a bust. They don't allow files > 250MB on the site. Several of the windows packages are bigger than that.
That is rather unfortunate. I wish they would published what their limits are in the first place. But I guess this is a deal breaker for using them. I vote that we go back to sourceforge for our primary download site, they
don't have problems like this.
I think I concur on that, at least for the next release. I'll bring this up in the release team to see how we move forward in the short term.
They've also been doing a pretty good job at cleaning up their reputation over the last few weeks. If we want to support two sites one for the source and one for the binaries, I don't think that's the end of the world, but I don't see it as ideal. Either way, can we also upload the source releases there even if it isn't the primary place to go? There are lots of links all over the internet that are pointing people there for downloads of boost, it would be sad if people following those only saw the old versions.
I would rather that all our official packages, source and binaries, be in one place for consistency and ease for end users. Again.. If anyone has alternatives for software distribution that can fit Boost's needs I would love to hear about it. Just because I like alternatives, and because some aspects of SF's way of doing things make it harder to automate the release process. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On 05.04.2016 23:34, Rene Rivera wrote:
On Tue, Apr 5, 2016 at 8:21 PM, Tom Kent
wrote: Sure.. Can you go here https://bintray.com/boostorg and hit the join button near the top. So I can give you access to upload the binaries.
Well that was a bust. They don't allow files > 250MB on the site. Several of the windows packages are bigger than that.
That is rather unfortunate. I wish they would published what their limits are in the first place. But I guess this is a deal breaker for using them.
I vote that we go back to sourceforge for our primary download site, they
don't have problems like this.
I think I concur on that, at least for the next release. I'll bring this up in the release team to see how we move forward in the short term.
Has releasing directly via github been considered ? (https://help.github.com/articles/creating-releases/) Stefan -- ...ich hab' noch einen Koffer in Berlin...
On Tue, Apr 5, 2016 at 10:37 PM, Stefan Seefeld
On Tue, Apr 5, 2016 at 8:21 PM, Tom Kent
wrote: Sure.. Can you go here https://bintray.com/boostorg and hit the join button near the top. So I can give you access to upload the binaries.
Well that was a bust. They don't allow files > 250MB on the site. Several of the windows packages are bigger than that.
That is rather unfortunate. I wish they would published what their limits are in the first place. But I guess this is a deal breaker for using
On 05.04.2016 23:34, Rene Rivera wrote: them.
I vote that we go back to sourceforge for our primary download site, they
don't have problems like this.
I think I concur on that, at least for the next release. I'll bring this
up
in the release team to see how we move forward in the short term.
Has releasing directly via github been considered ? (https://help.github.com/articles/creating-releases/)
It's been mentioned.. But I haven't had time to investigate further. Any help in finding out.. What limitations it has. What are the requirements for automating the uploads. What features it has as compared to SF and bintray. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
On 5 April 2016 at 13:28, Tom Kent
Can we put the windows binary builds up there as well? I had already uploaded them to sourceforge since no one told me the process had changed. Tom
FWIW I just added a link to your sourceforge upload to the release notes so that people can find it from there. I'm not sure what's the best way to present keys and signatures, so let me know. Will also add more detail to the download page at some point.
participants (6)
-
Daniel James
-
Glen Fernandes
-
Rene Rivera
-
Stefan Seefeld
-
Tom Kent
-
Vladimir Prus