Use polyglot-release for releasing

[lsuski]

🤔 What's changed?

Apply changes to allow using polyglot-release script for releasing

⚡️ What's your motivation?

Align with other cucumber repositories releasing process

🏷️ What kind of change is this?

• 📖 Documentation (improvements without changing code)
• 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)

♻️ Anything particular you want feedback on?

Adjusting RELEASING.md to contain new releasing process

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
• Users should know about my change
  • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[lsuski]

Requires cucumber/polyglot-release#101

[mpkorstanje]

You can also update the release guide to point to https://github.com/cucumber/.github/blob/main/RELEASING.md

[lsuski]

@mpkorstanje Is this tool working on Windows? Unfortunately I'm working on Windows

[mpkorstanje]

Unfortunately not. It is a shell script.

I also haven't used Windows for over a decade now. So I am not familiar with the state of the art around the Windows Subsystem for Unix or Dev containers. You can probably also get it to work in Cygwin. I reckon you might want to try to get it to work with one of those. If you run into troubles there I will be happy to help.

And if not, doing things manually is still an option, if a bit error prone.

[mpkorstanje]

I think we can merge this. Even if you can't use polyglot-release other people might.

Unless using a properties file for versions is not the preferred solution in general.