Releasing 0.6.0 with the merge request from issue #9

CHANGELOG.md

@@ -1,6 +1,11 @@
 Changelog
 =========
 
+#### 0.6.0 (2014-08-15)
+
+* Fix for mismatch between documentation and reality in the maxPartSize() and concurrentParts() options.
+* New feature: part size and concurrect part helpers can be chained now.
+
 ### 0.5.0 (2014-08-11)
 
 * Added client caching to reuse an existing s3 client rather than creating a new one for each upload. Fixes #6

README.md

@@ -6,6 +6,11 @@ A pipeable write stream which uploads to Amazon S3 using the multipart file uplo
 
 ### Changelog
 
+#### 0.6.0 (2014-08-15)
+
+* Fix for mismatch between documentation and reality in the maxPartSize() and concurrentParts() options.
+* New feature: part size and concurrect part helpers can be chained now.
+
 #### 0.5.0 (2014-08-11)
 
 * Added client caching to reuse an existing s3 client rather than creating a new one for each upload. Fixes #6
@@ -136,13 +141,15 @@ var UploadStreamObject = new Uploader(
   },
   function (err, uploadStream)
   {
+    uploadStream.maxPartSize(20971520) //20 MB
+
     uploadStream.on('uploaded', function (data) {
       console.log('done');
     });
 
     read.pipe(uploadStream);
   }
-).maxPartSize(20971520) //20 MB
+);
 ```
 
 ### stream.concurrentParts(numberOfParts)
@@ -159,14 +166,15 @@ var UploadStreamObject = new Uploader(
   },
   function (err, uploadStream)
   {
+    uploadStream.concurrentParts(5)
 
     uploadStream.on('uploaded', function (data) {
       console.log('done');
     });
 
     read.pipe(uploadStream);
   }
-).concurrentParts(5);
+);
 ```
 
 ### Tuning configuration of the AWS SDK

package.json

@@ -1,7 +1,7 @@
 {
   "name": "s3-upload-stream",
   "description": "Writeable stream for uploading content of unknown size to S3 via the multipart API.",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "author": {
     "name": "Nathan Peck",
     "email": "nathan@storydesk.com"