Update master from dev (nlog 5)

[304NotModified]

Master is behind currently.

Maybe also remove dev after this, and change to master. (Needs some updates to the docs and branch rules/protection)

[snakefoot]

Really hate source-control-merges. What about making a release-cuts ?

• create nlog4-branch from master
• create nlog5-branch from dev

And then create main-branch from dev for any work related to nlog6 (and drop master-branch + dev-branch)

Maybe before doing nlog6, then on might consider nlog51 with nullable-support.

[304NotModified]

We don't need those branches as we have tags?

Only if necessary hotfixes are expected for nlog 4, a branch would be nice.

[snakefoot]

I like that one only have to make a commit to a branch, and then automatically a new version is released.

[snakefoot]

I can see with all major version of NLog, then there have been a need to patch the previous major-version.

After the adventure with NLog v4 and v5, then I see that the Nlog-git-history has become huge mess, because of multiple huge branch-merges between dev and master.

Right now using minor-builds for NLog v5 (Ex. v5.2) for marking unwanted API as obsolete (but not making breaking changes), and guiding the NLog-users towards the future API of NLog v6.

I think we should continue to develop in dev-branch, but when the time arrives where pull-requests start piling up, that introduces wanted breaking changes, then nlog5-branch should be created with focus on mostly bug-fixes (maintenance-mode-only with cherry picking from dev-branch).