Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Toshio is now release manager for 2.8 and future 2.6 #51452

Merged
merged 1 commit into from
Jan 30, 2019

Conversation

abadger
Copy link
Contributor

@abadger abadger commented Jan 29, 2019

SUMMARY

Fix Roadmap docs for Toshio taking over release management duty

In the future, we might not want to list the RM by name (since it will be a dedicated person/team who is doing RM work).

ISSUE TYPE
  • Docs Pull Request
COMPONENT NAME

@ansibot
Copy link
Contributor

ansibot commented Jan 29, 2019

@ansibot ansibot added affects_2.8 This issue/PR affects Ansible v2.8 core_review In order to be merged, this PR must follow the core review workflow. docs This issue/PR relates to or includes documentation. needs_triage Needs a first human triage before being processed. small_patch support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels Jan 29, 2019
@dagwieers
Copy link
Contributor

Ok, so this information was also listed on the wiki:
https://github.com/ansible/community/wiki/RelEng

I think there's value in having a name (or GitHub handle) so you can address someone.

@ansibot ansibot removed the needs_triage Needs a first human triage before being processed. label Jan 29, 2019
@abadger
Copy link
Contributor Author

abadger commented Jan 29, 2019

jctanner and I were thinking of an email alias or mailing list. (although that doesn't take care of having a github handle).

@acozine acozine merged commit b0ac7d9 into ansible:devel Jan 30, 2019
@dagwieers
Copy link
Contributor

I guess it is not that important, PRs against a stable branch will end up with the release manager(s), and that's fine. Maybe the wiki page could include a list of people involved with Release Management (just like any other WG) instead in case people have questions or feedback.

abadger added a commit to abadger/ansible that referenced this pull request Jan 30, 2019
…sible#51452).

(cherry picked from commit b0ac7d9)

Co-authored-by: Toshio Kuratomi <a.badger@gmail.com>
@abadger abadger deleted the fix-release-manager-doc branch January 30, 2019 01:08
@abadger
Copy link
Contributor Author

abadger commented Jan 30, 2019

Yeah, the wiki page makes the most sense to me. Maybe have future roadmaps point to the wiki page for who to contact and just keep the wiki page up to date.

abadger added a commit that referenced this pull request Jan 30, 2019
…1452).

(cherry picked from commit b0ac7d9)

Co-authored-by: Toshio Kuratomi <a.badger@gmail.com>
@ansible ansible locked and limited conversation to collaborators Jul 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.8 This issue/PR affects Ansible v2.8 core_review In order to be merged, this PR must follow the core review workflow. docs This issue/PR relates to or includes documentation. small_patch support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants