Mark new releases as "internal preview", Alpha, Beta, Release (as its done in mature projects)

[IDA-RE-things]

Mark new releases/uploads as "internal preview", Alpha, Beta, Release. So users from whole world, will not go here to produce new and new bugreports for known issues, for functionality which are in development/testing stage, While it was only internal preview or "alpha".

[win32ss]

In future, I will lengthen the testing periods for Supermium releases. A release will be first made for testing purposes before it will be released for general usage.

[thinkpad4]

Thank you for this

[JoachimHenze]

I think it would also be good if the mature versions would see more releases.
E.g. most small fixes that are committed here by win32ss are really good.
Then comes the next huge Chrome update and some stuff may become incompatible again, or other stuff might stop to work due to googles upstream changes.

If we would see more releases with just fixes of win32ss, based on a fixed Chrome upstream state, that might improve the quality further.
Ofc that is significant maintenance.
So just added here as a thought.

[win32ss]

If Chromium had an ESR, Supermium would be based on it.

There isn't, but maybe I will rely on the LTC tags (3 versions behind stable). I admit that the rebasing does interfere a lot with the attempts to create deeper features, such as FTP, and furthermore every new upstream release seems to exhibit a lot of composition bugs (even on Mac OS, I see a lot of compositor bugs in Chromium even though the supported hardware/software combinations are very small there).

So I think the next release will be rebased on a newer revision of 122, and then eventually to LTC.