Closed annajung closed 2 years ago
cc @Bobgy @james-jwu @theadactyl @kimwnasptd
/lgtm
/lgtm
@annajung are you planning to make a PR?
Thanks for the reminder @thesuperzapper Since there is no opposition to the proposal, I went ahead and created a pull request https://github.com/kubeflow/community/pull/536 to move the release-related docs to the community repo. Please review when you can. Thanks!
Thanks, @annajung !
PR merged https://github.com/kubeflow/community/pull/536, closing the issue! thanks everyone
Based on the 1.4 release retrospective discussion, the 1.4 release team would like to propose that all release-related documentation be moved to the community repo and be managed by the release team members.
Currently, release-related documentations are located in the manifest/docs. During the 1.4 retro, the release team discussed that location of the docs are not very transparent to the community and that release related docs should be part of the community repo in addition to instructions for release blog posts and slide presentation
On behalf of the release team, I like to propose the following structure to be added to the community repo.
For every release, a new directory
release-x.x
will be created under thereleases
directory.Each
release-x.x
will contain the release timeline and the release team member information.I propose 1.5 release members to be included in the
OWNERS
file as reviewers and approvers to allow quick iteration of the release related documentation by the release team. For every future release,OWNERS
file gets updated to reflect the current member of the release team while allowing approver status for the previous release manager.