How does this repo maintain the same quality with https://github.com/aws/aws-sdk-js?

[Chengxuan]

Since this repo is a fork of the aws sdk repo, how does it pick up the bug fixes and functionality improvement of the aws sdk repo. Based on the statistics from npm:

The aws sdk repo are being used heavily and has more issues & pull requests. How does this repo keep itself up to speed with the aws sdk repo?

FYI @ashharrison90

[Chengxuan]

One example is #36 in which the same fix had been made for the aws sdk repo a year and 9 months ago.

That bug is not an edge case, it happens whenever there are more than 1 parts while uploading.
Our use case is back up our cloudant db to ibm cos3. We followed the example in here: https://github.com/cloudant/couchbackup/blob/master/examples/s3-backup-stream.js

The only difference is we are using the ibm sdk rather than the amazon sdk. FYI @ricellis

[barry-hueston]

Hi @Chengxuan,
thank you for your question.

We are currently working on synchronizing the patch levels with AWS, once complete our monthly releases cycles will be used to keep the patch levels in sync.

Thanks
Barry