| 2015-07-08 17:54:58 |
Irina Povolotskaya |
bug |
|
|
added bug |
| 2015-07-08 17:55:06 |
Irina Povolotskaya |
tags |
feature-plugins |
docs feature-plugins |
|
| 2015-07-08 18:01:40 |
Irina Povolotskaya |
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
- generate a gpg key using console gnupg
- create a tag after all files were approved and checked for LICENSE and copyright
For more details, you can contact Oleksandr Martseniuk or Simon Pasquier.
[1] https://wiki.openstack.org/wiki/Fuel/Plugins#How_to_tag_the_plugin_repository |
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
- generate a gpg key using console gnupg
- create a tag after all files were approved and checked for LICENSE and copyright
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 |
|
| 2015-07-08 18:02:05 |
Irina Povolotskaya |
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
- generate a gpg key using console gnupg
- create a tag after all files were approved and checked for LICENSE and copyright
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 |
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 [2]
- generate a gpg key using console gnupg
- create a tag after all files were approved and checked for LICENSE and copyright
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
[2]http://docs.openstack.org/infra/manual/drivers.html#merge-commits |
|
| 2015-07-08 18:03:27 |
Irina Povolotskaya |
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 [2]
- generate a gpg key using console gnupg
- create a tag after all files were approved and checked for LICENSE and copyright
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
[2]http://docs.openstack.org/infra/manual/drivers.html#merge-commits |
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 [2]
- 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
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
[2]http://docs.openstack.org/infra/manual/drivers.html#merge-commits |
|
| 2015-07-08 18:03:51 |
Irina Povolotskaya |
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 |
|
| 2015-07-09 08:25:04 |
Irina Povolotskaya |
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 [2]
- 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
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
[2]http://docs.openstack.org/infra/manual/drivers.html#merge-commits |
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
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 |
|
| 2015-07-09 08:34:50 |
Aleksandr Didenko |
fuel: status |
New |
Confirmed |
|
| 2015-07-09 09:50:46 |
Irina Povolotskaya |
fuel: importance |
Medium |
High |
|
| 2015-07-24 11:37:50 |
Irina Povolotskaya |
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
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 |
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
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 |
|
| 2015-07-24 11:38:28 |
Irina Povolotskaya |
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
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 |
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 |
|
| 2015-08-05 11:04:25 |
Irina Povolotskaya |
fuel: assignee |
Fuel Documentation Team (fuel-docs) |
Irina Povolotskaya (ipovolotskaya) |
|
| 2015-08-05 11:23:56 |
Irina Povolotskaya |
fuel: status |
Confirmed |
In Progress |
|
| 2015-08-05 11:24:31 |
Irina Povolotskaya |
fuel: status |
In Progress |
Fix Committed |
|
| 2016-05-13 18:38:04 |
Michele Fagan |
fuel: status |
Fix Committed |
Fix Released |
|
