genesis:integration_guidelines
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
genesis:integration_guidelines [2015/09/14 19:30] Frank Brockners |
genesis:integration_guidelines [2015/09/22 10:06] (current) Frank Brockners [OPNFV Project Integration Procedure] |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| * Description of the proposed requirement(s), including functionality provided and components affected, as well as the overall goal or purpose of these requirements | * Description of the proposed requirement(s), including functionality provided and components affected, as well as the overall goal or purpose of these requirements | ||
| * The OPNFV release which you would like to implement these requirements | * The OPNFV release which you would like to implement these requirements | ||
| + | * A preliminary list of dependencies: kernel version, kernel modules (and versions), additional packages needed, patches needed (even if created by the requesting project) | ||
| + | * A preliminary summary of management objects: configuration, parameters, logs, etc. | ||
| * A pointer to the repo/code where your feature is implemented and where the sources for the integration into the different deployment tools/installers are found. If the integration code for the different installers isn't done yet, please supply a timeline/milestones by when you plan to deliver the required code. | * A pointer to the repo/code where your feature is implemented and where the sources for the integration into the different deployment tools/installers are found. If the integration code for the different installers isn't done yet, please supply a timeline/milestones by when you plan to deliver the required code. | ||
| Line 34: | Line 36: | ||
| 6. **COMPLETE**: Jira tickets will be set to "resolved" if all installers have successfully implemented the new requirement. | 6. **COMPLETE**: Jira tickets will be set to "resolved" if all installers have successfully implemented the new requirement. | ||
| + | |||
| + | \\ | ||
| + | \\ | ||
| + | |||
| + | **Background**: The Genesis team uses the different tools in the following way: | ||
| + | |||
| + | * **Jira** is used “main entry gate” and “discussion forum” for requirements, where thr Genesis team discusses things and once the team has a common understanding a team member will create a patch, which reflects the discussion. This also means that the patch isn’t necessarily a 1:1 copy of the text in Jira. It will reflect the discussion the team hand and could also be more elaborate and more detailed than the simple high-level statement in Jira. This also means that the description of the patch in Gerrit is typically briefer and not the same as the contents of the patch. | ||
| + | * **Gerrit** is used as a review //and// voting vehicle, where the Genesis team also do final tweaks to and wordsmithing of the text and/or code entered. | ||
| + | * **Genesisreq git repository** is the official “source of truth” for the Genesis team. | ||
| ---- | ---- | ||
genesis/integration_guidelines.1442259035.txt.gz · Last modified: 2015/09/14 19:30 by Frank Brockners
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
