Preparing a v2.3.0 release

[kirchsth]

Hi @Potherca, @adrianvlupu, @IOrlandoni, @michiel and @stawirej:

Can we create a new v2.3.0 with all open pull requestes?

I have an updated structurizr/dotnet-extsions C4PlantUmlWriter and would prefere to use a official include with all available features.

Thank you and best regards
Helmut

PS.: Based on an official Structurizr v1.0.0 model it generated pictures (with v2.2.0) like

and with v2.3.0 like

[Potherca]

I plan on creating a 2.3 release this coming weekend, with all currently open MRs.

[kirchsth]

thank you

[Potherca]

Comment moved over from #161:

@Potherca: I would create a new release with following Issues/PR:
solved issues: #159,#157,#149,#146,#145,#139,#134,#21,#12
PRs: #161,#160,#158,#150,#147,#143,#141,#59

I agree with the outline stated above. I'll make a v2.3.0 branch to see if everything can easily be merge without to many conflicts, to save contributors the effort of having to keep updating/merging/rebasing their changes.

I also plan to make a develop branch, to merge upcoming MR into sooner, rather than running into a situation like this again. where we have MR from across 6 months that need integrating.

[Potherca]

All branches could be merged to the same branch without conflicts or issues. Will now commence merging all MRs.
All branches merged.

[Potherca]

All done! Release v2.3 is now a fact!

[kirchsth]

@Potherca, Thank you

Can you
a) update the moved comment and remove all issues which are not part of it

(156 could be obsolete as soon it is merged into PlantUML)
NOT included: 155, 154, 148, 85
Rejected?:104

b) add/link/close #159, #157 and #149 too (corresponding implementations were part of the PRs #160, #158 and #150)

BR
Helmut