Proposal: Use quarterly release names

[jpmcb]

I was on a flight last week and I realized that our "seasonal" releases (like "Summer 20xx" release, "Winter 20xx" release, etc.) are not very inclusive: there are people all around the world using Cobra and the idea of seasons may be completely flipped depending on where you're reading the release notes from.

This is not only confusing but isn't very mindful of our global community; it essentially presumes you're in the northern hemisphere. I'd like to remedy that, do the best thing for the whole community, and get the communities input.

---

Proposal - Quarterly

Using releases that denote which quarter in a year the release is coming out in would be a quick fix for this:

Winter  ▶️ Q1
Spring  ▶️ Q2
Summer  ▶️ Q3
Fall    ▶️ Q4

I'd love the communities feedback here!!!

[marckhouzam]

Very good point. The quarterly idea sounds very appropriate. Thanks for bringing this up.

👍

[umarcor]

it essentially presumes you're in the northern hemisphere

Actually, it assumes you are in the US or Canada. I guess it's related to 9/11 maintainers being located there.

Nonetheless, the American English season names were used for less than 1y in the 9y history of this project. We can stop using those terms the same way we started using them without prior discussion. IMHO, we should handle the issues/PRs through milestones only, which are precisely meant for that purpose. We don't need the additional complexity of naming the releases.

[jpmcb]

We don't need the additional complexity of naming the releases.

Named releases are nice for tracking what's going on and has been helpful (for at least me) when drafting changelogs, talking about stuff in public, etc.

[umarcor]

@jpmcb tags, milestones and names match unambiguously:

Tag	Milestone	Season name	Quarter name
v1.3.0	4	Fall 2021	2021 Q4
v1.4.0	5	Winter 2022	2022 Q1
v1.5.0	6	Spring 2022	2022 Q2
v1.6.0	7	Summer 2022	2022 Q3

[github-actions]

The Cobra project currently lacks enough contributors to adequately respond to all issues. This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed.
  You can:
• Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening