We need your help to make VersionOne SDK.Python a useful integration. While third-party patches are absolutely essential, they are not the only way to get involved. You can help the project by discovering and reporting bugs and helping others on the versionone-dev group and GitHub issues.
Before reporting a bug on the project's issues page, first make sure that your issue is caused by VersionOne Integration for Buy A Feature, not your application code (e.g. passing incorrect arguments to methods, etc.). Second, search the already reported issues for similar cases, and if it has been reported already, just add any additional details in the comments.
After you made sure that you have found a new bug, here are some tips for creating a helpful report that will make fixing it much easier and quicker:
- Write a descriptive, specific title. Bad: Problem with filtering. Good: Scope.GetThisAndAllChildProjects() always returns an empty list.
- Whenever possible, include Class and Method info in the description.
- Create a simple test case that demonstrates the bug (e.g. using NUnit).
Coming soon! We are still migrating this project from our private Subversion repository. If you are interested in contributing code to this project, please contact Ian Buchanan.
Open source software evolves over time. A young project may be little more than some ideas and a kernel of unstable code. As a project matures, source code, UI, tests, and APIs will become more stable. To help consumers understand what they are getting, we characterize every release with one of the following quality bands.
The initial idea of a product. The code may not always work. Very little of the code may be covered by tests. Documentation may be sparse. All APIs are considered "private" and are expected to change. Please expect to work with developers to use and maintain the product.
The product is undergoing rapid growth. The code works. Test coverage is on the rise. Documentation is firming up. Some APIs may be public but are subject to change. Please expect to inform developers where information is insufficient to self-serve.
The product is stable. The code will continue to evolve with minimum breaking changes. Documentation is sufficient for self-service. APIs are stable.