RFI: High Level Description of the point release process (ie v0.20.3)

[sliptonic]

We need an outline of how an interim release is done.

[adrianinsaval]

In previous releases when enough commits got backported to the stable branch to warrant a new release I think a windows installer was built by @donovaly then if no problems where reported by testers the release was tagged and then @looooo triggered conda builds for supported platforms at https://github.com/conda-forge/freecad-feedstock and created a branch for the bundles at https://github.com/FreeCAD/FreeCAD-Bundle then the generated assets are reuploaded to the release page in the main repo, other maintainers take care of other paltforms (me for flatpak, @luzpaz or @ppd for snap)

In the future it would be desirable to first check if we can still build on all major platforms before tagging a release, pushing an update to a tag is undesirable as some distros may not realize this happened and incorrectly ship the initially tagged version (this happened once on archlinux)

[luzpaz]

Are we updating translations from point releases ? (we haven't in the past)

[luzpaz]

Also, website download page reflecting FreeCAD version point release update and wiki page updates (like https://wiki.freecad.org/AppImage)

[adrianinsaval]

Are we updating translations from point releases ? (we haven't in the past)

Unless crowdin can do versioned translation that's not practical to do. Maybe for the first point release if we're sure there hasn't been changes to displayed strings on master yet, IIRC we did that for 0.20.1