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/15 16:53] Jonas Bjurel |
genesis:integration_guidelines [2015/09/22 10:06] (current) Frank Brockners [OPNFV Project Integration Procedure] |
||
|---|---|---|---|
| Line 36: | 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. | ||
| ---- | ---- | ||