Specs/ directory and posting it for review. Specifications are proposed for a given release by adding them to the You can typically find an example spec in specs/template.rst.Ĭheck the repository for the project team you’re working on for specifics The layout of the repository will typically be something like: Is used to hold approved design specifications for additions and changes to Many OpenStack project teams have a -specs repository which Working on Specifications and Blueprints ¶ Section of the OpenStack Git Commit Good Practices wiki page. Will update and people will be able to find the related story.Īlso see the Including external references It’s currently best to note both story and task so that the task status If the patch is abandoned, the task status will change back to ‘todo’. The story will automatically change status from ‘active’ to ‘merged’. When all tasks in a story are marked ‘merged’, ‘review’ while the patch is in review, and then ‘merged’ once the Mentioning the task will change the task status in StoryBoard to Mentioning the story will create a handy link to the story from gerrit,Īnd link to the gerrit patch in StoryBoard. When you upload a review, include the bug in the commit message forĪutomatic updates back to Launchpad or StoryBoard. If you find a bug that you wish to work on, you may assign it to yourself. Learn more about working with bugs for various projects at: If the bug is still being worked on, if not, unassign them and mark them Review stale In Progress bugs: Work with assignee of bugs to determine “Incomplete” has been provided, determine if more information is requiredĪnd provide reminders to the bug reporter if they haven’t responded after Review incomplete bugs: See if information that caused them to be marked Solve inconsistencies: Make sure bugs are Confirmed, and if assigned There are 4 key tasks with regards to bugs that anyone can do:Ĭonfirm new bugs: When a bug is filed, it is set to the “New” status.Ī “New” bug can be marked “Confirmed” once it has been reproduced Reports regularly when looking for work to complete. Git remote rm gerrit Development Workflow ¶ Working on Bugs ¶īug reports for a project are generally tracked on Launchpad at You should run the following command before “git review -s”: Keep in mind that you will need to generate anĬonnection. Using https) then you can configure git-review to use an https endpoint Over non-standards ports might be blocked (or you need to access the web Git-review normally communicates with Gerrit using SSH over port 29418 with Individual Contributor License Agreement, see these detailed Projects that are part of OpenStack project require signing the Extra Gerrit account setup steps ¶ OpenStack Individual Contributor License Agreement ¶ You can find the OpenDev community in the #opendev IRC channel on OFTC.įor further information about the use of IRC in OpenStack, see Preventing anyone else from using it at all. While you’re not connected, or even (with some additional settings) This willĪllow you to reclaim your name later if someone starts using it Your IRC Nick since it’s how they’ll know you’re you. Through OFTC on a regular basis, it’s also recommended you Register If you’re going to be interacting with others If you do not know how to connect to OFTC, the Connecting to OFTCĭocument will help. IRC so that one can ask questions if one encounters issues with other It is recommended to start by getting set up on Projects often requires interacting with other developers in IRCĬhannels on OFTC. Gerrit Code Review System, effective development in OpenDev hosted While development on OpenDev only requires an account on the OpenDev Only extra recommended steps will be described here. The steps necessary to create a Gerrit account are described in Specifics that should be understood while contributing to projects The goal of this document is to walk you through the concepts and
0 Comments
Leave a Reply. |