Filing issues is a great way to contribute to the ASP.NET Redis Providers. Here are some guidelines:
- Include as much detail as you can be about the problem
- Point to a test repository (e.g. hosted on GitHub) that can help reproduce the issue. This works better than trying to describe step by step how to create a repro scenario.
- Github supports markdown, so when filing bugs make sure you check the formatting before clicking submit.
Just follow the existing patterns already present in the code.
We actively develop in the master branch. This means that all pull requests by contributors need to be developed and submitted to the master branch.
When we release a new NuGet package, we create a tag for it.
Before we can accept your pull-request you'll need to sign a Contribution License Agreement (CLA). You can sign ours here. However, you don't have to do this up-front. You can simply clone, fork, and submit your pull-request as usual.
When your pull-request is created, we classify it. If the change is trivial, i.e. you just fixed a typo, then the PR is labelled with cla-not-required. Otherwise it's classified as cla-required. In that case, the system will also also tell you how you can sign the CLA. Once you signed a CLA, the current and all future pull-requests will be labelled as cla-signed. Signing the CLA might sound scary but it's actually super simple and can be done in less than a minute.
Make sure you can build the code. Familiarize yourself with the project workflow and our coding conventions. If you don't know what a pull request is read this https://help.github.com/articles/using-pull-requests.
Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. Note that all code submissions will be rigorously reviewed and tested by the Azure Cache Team, and only those that meet the bar for both quality and design/roadmap appropriateness will be merged into the source.