Create a Release calendar about sig-release

[justaugustus]

Thanks for adding this, @nikhita!

[justaugustus]

This has since been added to the RT Lead Handbook: https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/release-lead.md

/close

[idvoretskyi]

@justaugustus are you speaking about the Google Calendar?

If yes, we may incorporate it into the Community-wide calendar. /cc @castrojo

[justaugustus]

Oooo, putting in the Community calendar would work nicely!

[castrojo]

I can either add someone to the release team to the main community calendar to add the events directly, or you can share individual events from your existing calendar with [email protected] to put them on the community calendar.

Let me know which you would prefer!

[justaugustus]

@castrojo cool! If you add me I can populate the release events for the calendar. :)
mylastname @ redhat.com

[castrojo]

Done! Is there a checklist or some thing we can add this to as a step in the release process? That way we can rotate out access to the calendar as needed from release to release.

…

On Tue, Apr 10, 2018 at 9:08 AM Stephen Augustus ***@***.***> wrote: @castrojo <https://github.com/castrojo> cool! If you add me I can populate the release events for the calendar. :) mylastname @ redhat.com — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#125 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABNJ7VhCJDfszJY6slEwTpRUrF2juCFeks5tnK7IgaJpZM4TN5-o> .

[justaugustus]

@castrojo Thanks for hooking up access.
I've just updated the Community calendar to include the v1.11 release key dates and will shoot out a quick note to the group.

Good point on adding the step to the release process.
I'll PR adding that step, but we need to decide who should be doing it as well.

Communications? Release Manager? Whoever volunteers for it?
Thoughts @jberkus / @idvoretskyi ?

[jberkus]

This should probably go into the Release Lead Handbook: https://github.com/kubernetes/sig-release/blob/master/release-process-documentation/release-team-guides/release-lead.md

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[nikhita]

/remove-lifecycle stale

This should probably go into the Release Lead Handbook

/assign

[nikhita]

The 1.12 schedule is already present in the community calendar.