-
Notifications
You must be signed in to change notification settings - Fork 514
How to Report Bugs and Make Feature Requests
You can report a bug by opening a new issue here. You have to complete the template section for bug reports. Be sure to specify all sections:
- Version of OpenNebula
- Component
- Brief description
- Expected behavior
- How to reproduce
After an internal analysis, a bug issue will be set to one of the following statuses:
- Pending: needs to be verified
- Accepted: the bug has been verified and a priority assigned based on its severity (Low, Normal, High)
- Planned: (Accepted with a specific milestone)
- Closed: the issue is fixed, could not be reproduced (worksforme) or duplicates another one
You can report a bug by opening a new issue here. Be sure to specify all sections in the template:
- Brief description of the new functionality
- How are you going to use this new feature? Why do you need it?
- Describe any changes to current interfaces including Sunstone, CLI and/or API
The issue will be used to track the discussions about the new feature. You should also specify if you are planing to allocate resources to implement the new feature. Once the new issue is created, you can bring it up for discussion on the Community Forum.
We will contact you as soon as possible to gather more information and to give you initial feedback about your Request issue. This may take some time, and is usually not done until the next release cycle, at the earliest. When we update the roadmap of the project and plan the features for the next release, we prioritize:
- The features demanded by the projects and organizations sponsoring the open-source project
- The most demanded features by the community.
After an internal analysis, your Request issue is categorized and will be Pending in the Backlog until:
- It is interesting for the OpenNebula community and will be added as Accepted in the Backlog
- It is decided that is not in the scope of the project and Closed
Backlog issues are long-medium term roadmap features to be implemented in OpenNebula. The priority of the issues will be graded (Low, Normal, High).
A backlog issue remains Accepted until:
It is assigned to a Milestone and so moved to the Feature list
- It is Closed because it is no longer interesting for the OpenNebula Community
- Feature issues are short term Accepted features with an assigned milestone.
You can use the GitHub Pull Request model to submit a bug or feature patch.
- Fork it
- Create a branch (
git checkout -b my_markup) - Commit your changes (
git commit -am “My changes”) - Push to the branch (
git push origin my_markup) - Create a Pull Request to this repository from your new branch
It is understood that your patch addresses an open issue in GitHub. Update the issue with a full description of what you have done, describe your tests, and include a link to the Pull Request. When your patch is reviewed, it may be accepted “as-is” or you may be asked to make changes. Code commits (after review) will be implemented as named commits.
A. Use OpenNebula
- Release Packages
- Release Schedule
- Release Policy
- Product Roadmap
- Community Forum
- Documentation
- Documentation Archives
- QA & Testing
- Bugs & Feature Requests
B. Code OpenNebula
- Software Repo
- Documentation Repo
- How to Contribute
- Localization
- Sign your Work
- Vulnerability Management
C. Create an Add-on
D. Spread the Word