Update release process

[niccokunzmann]

Closes issue

• Closes Next release todos #1293

Description

This updates the release process to what I actually did. It should work like this for the next releases.

I could remove some sections about the version switcher.

Readthedocs does not create a version for the tag, so that step can also be removed.

A commit on branch 7.x has been created that shall be carried forth through the merges of main that keeps the version switcher disabled.

release branch steps are done on main now.

How to proceed

Please correct the formatting or text if you need to and merge: This is a living document, and it should be merged before the next release. If there are procedural mistakes (content), they will be corrected with the next release. You can point them out in an issue or make edits here. If you want to adjust the style, not the content, please go ahead and do that and then merge.

---

📚 Documentation preview 📚: https://icalendar--1350.org.readthedocs.build/

[read-the-docs-community]

Documentation build overview

📚 icalendar | 🛠️ Build #32730757 | 📁 Comparing 1b853d7 against latest (ff367c1)

  🔍 Preview build  

14 files changed · ± 14 modified

± Modified

• 404.html
• genindex.html
• contribute/index.html
• contribute/maintenance.html
• reference/changelog.html
• reference/api/icalendar.cal.alarm.html
• reference/api/icalendar.prop.dt.html
• reference/api/icalendar.prop.dt.period.html
• reference/api/icalendar.prop.recur.html
• reference/api/icalendar.prop.recur.weekday.html
• and 4 more...

[niccokunzmann]

2e87032 is part of main already.

[stevepiercy]

See revised steps to automate the change log process in #1389

[SashankBhamidi]

@stevepiercy Do you wish I take over this PR? If so, I can next week once I'm done with some OWC work and a be back from a 2 day trek.

[stevepiercy]

@SashankBhamidi I'll rebase it and take care of a few things that I understand, then tag you to take over. Thank you!

[SashankBhamidi]

Resolve conversations once you're done so I can start fresh

[stevepiercy]

@SashankBhamidi I'm all done. Tag! You're it!

I'd be open to get together on a call and walk through this together with you for the release of 7.1.1.

[SashankBhamidi]

Thanks @stevepiercy! Few things:

[stevepiercy]

@SashankBhamidi this is ready for review. If it looks good, please merge it, then try it out with a new release. If we need to make a second new release, that would be OK, too. Thank you!

[SashankBhamidi]

@stevepiercy Thanks!

Step 8 still has a problem for the major release path though.

[stevepiercy]

@SashankBhamidi one more review, please. I think this time, I got it all down.

[SashankBhamidi]

LGTM, both paths verified in a scratch repo. Approving. Thanks!

[SashankBhamidi]

I'll merge this soon. I don't have access to my laptop right now.

[stevepiercy]

@SashankBhamidi I approved it, and set it to auto-merge. It should merge in about 10 minutes.

Then can you do a release? I really want to fix the version switcher, which broke with the last release. That thing is tricky.

[coveralls]

Coverage Report for CI Build 26016285081

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Coverage remained the same at 97.775%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	12624
Covered Lines:	12348
Line Coverage:	97.81%
Relevant Branches:	770
Covered Branches:	748
Branch Coverage:	97.14%
Branches in Coverage %:	Yes
Coverage Strength:	5.86 hits per line

---

💛 - Coveralls

[SashankBhamidi]

@stevepiercy Done and dusted!