[Fuel Plugins SDK] SDK lacks information about creating a tag in the plugin's repo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Irina Povolotskaya |
Bug Description
SDK lacks information about a key stage when working with repo [1].
To create a tag for repo, plugin dev team (or, specifically, a team member) should:
- have core reviewer's rights
- enter release group of the project (so, the request for repo creation MUST contain the both creation of core and release groups with members listed)
- generate a gpg key using console gnupg
- use master -> stable branching workflow as common practice
- create a tag after all files were approved and checked for LICENSE and copyright
- all fuel-plugins must have pushMerged rights
- all fuel-plugins must have pushSignedTag with a -release group (????) - need to clarify this
For more details, you can contact Oleksandr Martsyniuk or Simon Pasquier.
[1] https:/
tags: | added: docs |
description: | updated |
description: | updated |
description: | updated |
summary: |
- [Fuel Plugins SDK] SDK lacks information about generating gpg keys + [Fuel Plugins SDK] SDK lacks information about creating a tag in the + plugin's repo |
description: | updated |
Changed in fuel: | |
status: | New → Confirmed |
description: | updated |
description: | updated |
Changed in fuel: | |
assignee: | Fuel Documentation Team (fuel-docs) → Irina Povolotskaya (ipovolotskaya) |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
High priority as current dev teams must be aware about the case.
Without these intructions, validation procedure is stuck.