[boost] Moving away from SourceForge

Subject: [boost] Moving away from SourceForge
From: Louis Dionne (ldionne.2_at_[hidden])
Date: 2017-01-22 11:35:32

Hi,

I know this has been discussed in the past, but I would like to revive the
discussion about moving away from SourceForge as Boosts' release hosting
provider. SourceForge has at least the following issues:

- There is no way of controlling the format when downloading an archive of
  the latest release. This can break people that rely on this in their CI
  scripts. For example, Metabench's[1] CI was broken for a while when the
  archive changed from .bz2 to .zip.

- SourceForge has been in the middle of some controversies[2].

- Their reliability has not been so great. In the past year, I've had quite
  a few of my Travis jobs fail due to SourceForge being unresponsive.

There are most likely other concerns, but these are the ones that really
bite
me as a user right now. Am I the only one? If there's some push to do the
move,
the two main candidates I see would be

- GitHub's native hosting
- Bintray

Thoughts?
Louis

[1]: https://github.com/ldionne/metabench
[2]: https://en.wikipedia.org/wiki/SourceForge#Controversies

--
View this message in context: http://boost.2283326.n4.nabble.com/Moving-away-from-SourceForge-tp4691184.html
Sent from the Boost - Dev mailing list archive at Nabble.com.