flatten changelog into current release and release history for ease of maintenance

[jodygarnett]

This pull request addresses concerns raised in #7886

This is blocked by:

• Do we need to restore page html suffix to documentation pages? #7705

To address we will need to coordinate an update across documentation branches:

• main: flatten changelog into current release and release history for ease of maintenance #7887
• 4.2.x: pending feedback of above
• 3.12.x: pending feedback of above
• 2.10.x: 2.10.x theme updates, includes workflow for deploy to gh-pages #7885

Changes

A banner will be displayed when 4.4 passes into maintenance.

With this change the navigate and changelog match up:

Release History is one page that is hopefully easier to maintain:

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[jodygarnett]

This change has gone stale, need to work on moving these kind of changes faster

[juanluisrp]

@jodygarnett I've rebased main and fixed the conflicts. I've added a entry in the navigation tree for 4.2.9 version under changelog and a link in the entry in the change-log/index.md to keep an easy access to the latest version of that branch. I've also added 4.4.4 to the history list.

---

[juanluisrp]

LGTM.

[josegar74]

@jodygarnett with mkdocs serve I get the following, with the 2 entries None:

With mike serve I get the old format. I guess this doesn't take the local changes?

[jodygarnett]

i do not know what is up with the None entries? did you do a clean?

[josegar74]

i do not know what is up with the None entries? did you do a clean?

@jodygarnett it is related to the version of mike. I had 1.5.3, but upgrading to 1.6.0 works fine.

[jodygarnett]

lol - I just figured that out also, adding instructions on how to update to the readme. Also removing the docker instructions (as we have have some non standard plugins now that are not included with default mkdocs docker image).