> Summary:
>
> Boost downloads will be hosted at a new location, with the URL format
> https://archives.boost.io/release/1.85.0/source/boost_1_85_0.tar.gz
>
> Details:
>
> During the last couple of years the Boost downloads have been hosted on
> JFrog Artifactory, and before that on Bintray. JFrog has been very
generous
> in providing the bandwidth and hosting services.
>
> Recently, bandwidth increased into the 150TB/month range. JFrog requested
> the download be moved behind a CDN, or migrated to another service
entirely.
>
> At the C++ Alliance, we have set up load balanced AWS EC2 instances, and
> configured a Fastly CDN, on the domain archives.boost.io. Fastly offered a
> discounted bulk rate based on the large amount of traffic.
>
> The boost.org website now shows links to the new CDN.
>
> If you are using any automated scripts that point to jfrog.io, the
existing
> JFrog links will continue to function until December 2024.
>
>
> - Sam Darwin
I maintain the Boost spack package[1]. The versions currently available
there go back to 1.39.0. However, the versions available on
archives.boost.io only go back to 1.63.0. Are the older versions going to
be available there or will they remain on the sourceforge hosting?
Thanks.
- Tim
[1]
https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/package…
P.S. I am terribly sorry if this messes up the thread. I get my messages in
digest form and could not for the life of me figure out how to reply to
your email directly to the list.
Hi,
Feature request:
I would like the JSON parse to inform me that duplicate keys were encountered.
I believe they are currently silently handled (with a last-one-wins strategy).
Thanks,
John Abbott
Hi,
Since the current Boost webserver and mailing list are quite out-of-date,
it makes sense to consider the upgrade path.
Mailman3 is a complete rewrite of the mailing list software. It's designed
with multiple components: hyperkitty archives, postorius, and mailman-core.
Dev instances have been installed. If you have any curiosity about testing
mailman3 using your local email client, or sending feedback about the
mailman3 experience, you can subscribe at https://lists.preview.boost.org.
Send/receive emails.
If you notice problems using mailman3, open an Issue at the Github
repository cppalliance/boost-mailman. Now is the best time to discover
issues, rather than after deployment.
Lists at https://lists.preview.boost.org won't be maintained permanently.
Any emails or accounts there will eventually be deleted. It's only a
staging type environment.
Working with the web developers we are planning to modify the appearance of
the front-end UI, adding css styles, links to the boost website, and so on.
Keep an eye on the test lists for updates.
In the future when "going live", the idea will be to schedule (extended)
planned downtime, and have a new server fully replace "lists.boost.org".
Which specific boost mailing lists should be kept? It would be easier to
avoid migrating all lists, if some of them are not active.
Best Regards,
Sam Darwin
C++ Alliance
