Github tagging

[antonioleal]

Not really an Issue, more a request:

It is possible at some point to start creating Github Tags so software packages can be made downstream?

Tks
António

[wfjm]

This is the revival of an old discussion that was never finished. It came up again in connection with the migration of the build system and fizzled out again. Before you can set tags and define releases, you have to have a clear picture of what a release target is, what verification is done beyond the quick CI/CD flow tests, and last but not least, you have to have the will to write a meaningful CHANGELOG and release notes.

[bscottm]

@antonioleal: Packaging is something I'm working on and tagging is going to be a important tool.

[bscottm]

@antonioleal: My fork, bscottm/open-simh, now has two tagged releases -- simh-4.0.0-alpha1 and simh-4.0.0-alpha2. Github Actions CI/CD will automagically create a release when a new repo tag starting with "v" or "sim-h" is created.

[antonioleal]

@antonioleal: My fork, bscottm/open-simh, now has two tagged releases -- simh-4.0.0-alpha1 and simh-4.0.0-alpha2. Github Actions CI/CD will automagically create a release when a new repo tag starting with "v" or "sim-h" is created.

That's a start, thanks! Hope the main project will follow as well.

[XVilka]

Looks like now is a good time to make a new release, it's super-outdated in many distributions/systems: https://repology.org/project/simh/versions

[XVilka]

@pkoning2 @bscottm since there were many updates and now a good CI was setup, maybe it's time to make a new release?

[bscottm]

@pkoning2, @XVilka: All that need be done is to add a tag that starts with "v" or "simh", e.g., "v4.1.1" or "simh-4.1.1". That'll trigger a CI/CD workflow with all of the packages published as a release.