Release Event Hub Track 2 Library Preview 1

[AlexGhiondea]

Goal: Release Preview for Track 2 of Event Hub

The existing JS SDK for Event Hubs was only made GA just last year (Sept 2018). For Track2, we will be working on top of the existing SDK and releasing newer versions rather than creating a whole new library. The entire API surface is in scope

Non-breaking changes

• Repo readiness [Event Hubs] Update README as per template #2638, [Event Hubs] Add missing Contributing.md and License files to the project #2639. [Event Hubs] Remove .npmignore file #2652, [Event Hubs] Update package.json files to have sideEffects set to false  #2653, [Event Hubs] Update tsconfig to comply with guidelines #2655
• Port over applicable improvements from Service Bus [Event Hubs] Port bug fixes from Service Bus #2688
• Improving existing samples and Quick starts [Event Hubs] Consumer Group setup #1975, [Event Hubs (EPH)] Standardize samples and use published package #2636, [Event Hubs Service Bus] Samples should have Copyright text #2711, [Event Hubs] Standardize samples and use published package #2634, [Event Hubs] Update instructions on samples in docs #2637
• Move amqp-common to central repo and ship an update Release amqp-common package from the main repo #2704
• ✋ Browserification [Event Hubs] Add rollup for browser mode #2808, [Event Hubs] Add tests for browser mode #2809

Extend current APIs

• Propose API changes to include cancellation [Event Hubs] Investigate how cancellation and timeouts can fit into our APIs #2641
• Propose API changes to include retries and timeouts [Event Hubs] Review retry logic against the guidelines #2661
• Propose API changes to include logging [Event Hubs] Investigate how current logging mechanism can fit into logging levels #2662
• Review User facing API [Event Hubs] User facing API Review #2718

Implementation of API proposals:

• Retries for all operations except receive [Event Hubs] Allow users to configure retry options in send requests #2831, [Event Hubs] Allow users to configure retry options in apis using the $management link #2834, [Event Hubs] Retry options on the receiver #3184
• Refactor to support creating of senders and receivers: [Event Hubs] Implement createSender() end to end #3170, [Event Hubs] Review AMQP link lifecycle for Sender #3172, [Event Hubs] Ensure receiver is functional #3175, [Event Hubs] Review AMQP link lifecycle for Receiver #3176
• Constructor overloads, reduce static helpers for client creation: [Event Hubs] Consider combining ClientOptionsBase and ClientOptions #2920, [Event Hubs] Add constructor that takes connection string #3173,
• Cancellation on individual operations [Event Hubs] Support cancellation token in send requests #2836, [Event Hubs] Support cancellation token in receiveBatch #2837, [Event Hubs] Support cancellation token in streaming receiver #2838, [Event Hubs] Support cancellation token in apis using the $management link #2839
• Support multiple receive operations on same receiver [Event Hubs] Receive Batch should re-use its batching receiver #3304, [Event Hubs] Multiple receive operations on the same receiver #3309, [Event Hubs] Iterator for receiver should receive events in the background #3308, [Event Hubs] Ensure both batching and streaming receivers are able to re-establish links on retryable errors #3310
• Error Handling [Event Hubs] Re-visit all parameter validations #2660

Docs

• [Event Hubs] Review typedocs on each public member #2657, [Event Hubs] Update Samples and README after proposed API changes are in #2850

[ramya-rao-a]

Closing this epic as we have now released 5.0.0-preview.1 of the @azure/event-hubs library.
Changelog can be found at https://github.com/Azure/azure-sdk-for-js/releases/tag/%40azure%2Fevent-hubs_5.0.0-preview.1

[chradek]

The package can be found on NPM at https://www.npmjs.com/package/@azure/event-hubs/v/5.0.0-preview.1.