Plans for a v2.3 release?

[Potherca]

I think it is time to start thinking about a new release... So what should be included in a v2.3 release?

• Another round of adding missing icons

  • #48
  • #49
  • #50
  • #51
  • #52

• #41

• #46

• A CONTRIBUTING.md file

  Full Changelog: https://github.com/plantuml-stdlib/Azure-PlantUML/compare/v2.2...master

  This issue is a placeholder for all tasks that need to be completed to release a new version (2.3.0):

  • [ ] Create a separate release/2-3 branch (as was done for previous releases). ^{So users can include a versioned file instead of requring main / HEAD}
  • [ ] Update the versioned links in the README.md file (see fe13039) ^{So the documentation points to the latest available changes}
  • [ ] Check if anything else that needs changing. Copyright year? Any contrib files? URLs? If so, add to the version branch. ^{Making everything is in order before the release, so we do not have to make minor releases afterward}
  • [ ] Open an MR to incorporate the changes needed for version release into the main branch. ^{So there is a fixed/traceable moment in time that marks the change}
  • [ ] After review, merge the changes but DO NOT DELETE THE VERSION BRANCH. We want to keep that around. ^{So users can include a versioned file instead of requiring main / HEAD}
  • [ ] Create a new release of the latest changes (using "Generate Release Notes"). ^{So there is a fixed/traceable moment in time that marks the change}
  • [ ] Open an MR at plantuml/plantuml-stdlib ^{So the latest changes are available to all users}
  • [ ] Mark the version branch as protected ^{So history cannot be falsified (whether by accident or on purpose).}

  It also serves to be a first step in documenting how releases are made. Eventually, a complete write-up should be added as part of a CONTRIBUTING.md

Anything else that needs adding?