-
Notifications
You must be signed in to change notification settings - Fork 172
Announcements about S3 BitTorrent discontinuation shouldn't be buried in the commit history #27
Comments
Hello But it seems to me that still the official docs site doesn't cover the deprecation at all. In addition, there is a misleading article that talks about how to get the torrent for a specific object, which you can find here. We need to remove similar misleading articles and possibly add permanent notice on the site to tell developers not to use this deprecated service. |
Is it possible that the AWS changed its mind between May 13 and 19, and retracted the announcement? |
I don't think that's too misleading, it's describing how to use the S3 BitTorrent APIs – which will presumably continue to work until next April.
Yes, that's what I'm asking for.
I'd be very surprised if they did, and if they did, I'd expect them to have restored the feature page for S3 BitTorrent. |
Closing this issue or pull request in advance of archiving this repo. For more information about the decision to archive this repo (and others in the "awsdocs" org), see the announcement on the AWS News Blog. |
Commit 0d17598 (13 May) announced the deprecation plan for S3 BitTorrent:
The entire page was then removed in commit 7a83e40 (19 May).
At present, the discontinuation notice doesn't appear anywhere in the S3 documentation; all mention of BitTorrent has been completely removed. If somebody is wondering if this feature is still supported or for how much longer it'll be available, that's pretty difficult to find right now.
It would be helpful if there was a page with this warning as part of the S3 documentation, so people could find this information more easily than poking through the commit history.
The text was updated successfully, but these errors were encountered: