[Fuel Plugins SDK] SDK lacks information about creating a tag in the plugin's repo

[Irina Povolotskaya]

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://wiki.openstack.org/wiki/Fuel/Plugins#How_to_tag_the_plugin_repository

[Irina Povolotskaya (ipovolotskaya)]

High priority as current dev teams must be aware about the case.
Without these intructions, validation procedure is stuck.

[Mateusz Matuszkowiak (mmatuszkowiak)]

By the way, regarding the:
- all fuel-plugins must have pushSignedTag with a -release group (????) - need to clarify this

It came from one openstack-infra Core developers, who suggested that pushSignedTag should have a "dedicated" (non-core) group, i.e should ending with -release.

With Kind Regards,
Mateusz

[Irina Povolotskaya (ipovolotskaya)]

Please, check this section https://wiki.openstack.org/wiki/Fuel/Plugins#How_to_create_a_project