Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event Hubs Client Library for .NET - January Milestone #9040

Closed
18 tasks done
jsquire opened this issue Dec 9, 2019 · 0 comments
Closed
18 tasks done

Event Hubs Client Library for .NET - January Milestone #9040

jsquire opened this issue Dec 9, 2019 · 0 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs

Comments

@jsquire
Copy link
Member

jsquire commented Dec 9, 2019

For general summary and goals, please see: Release Event Hubs Track 2 Library (#442). The work items linked to this issue herein represent the tasks needed to produce the .NET Event Hubs client library for the current milestone.

Design, Review, and Planning

  • Review the final API skeleton with the .NET feature team and architect; determine potential areas for tuning
  • Create issues and perform resource planning for the next milestone

Implementation

Stress and Stability

  • Stress and Stability Testing (#9044)
  • Update Service Stress Client for new API (#9046)
  • Test Stabilization (#9047)
  • Fix potential null dereference in the AmqpMessageConverter (#9052)
  • Exception when resuming processing from a checkpoint (#9213)

Diagnostics

  • Integrate logging into the Event Processor Client and associated types (#8571)
  • Integrate logging into the Blobs Event Processor Store types (#8663)

Configuration

  • Review project file configuration and overrides (#9050)

Release and Documentation

  • Create a Migration Guide (#9065)
  • Reference documentation (#9041)
  • Changelog (#9041)
  • Samples (#9042)
  • Update Azure SDK repository change log
  • Release Event Hubs core package to Nuget
  • Restore package reference to Event Hubs core from Event Hubs processor after package is released
  • Release Event Hubs Processor package to Nuget
@triage-new-issues triage-new-issues bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 9, 2019
@jsquire jsquire added the Epic label Dec 9, 2019
@triage-new-issues triage-new-issues bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 9, 2019
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. Event Hubs labels Dec 9, 2019
@jsquire jsquire self-assigned this Dec 9, 2019
@jsquire jsquire added this to the [2020] January milestone Dec 9, 2019
@jsquire jsquire closed this as completed Jan 29, 2020
@AlexGhiondea AlexGhiondea reopened this Mar 2, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Mar 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Development

No branches or pull requests

4 participants