[Comment] Release tags don't map to source changes, hard to tell what's actually changing between versions

[mrkesu]

This is a very confusing repo to follow. I see you are creating release tags pointing at a stale commit and just attaching source code assets to the new release, but all traceability is lost so it's very difficult to see what is happening in the source between one release and the next. It's just being version-bumped and re-released without meaningful source changes tracked in git... Why?

You also have a docker image which seems to be built from some other file structure than whats in the repo or even the "Source code (zip)", it references a devops/ and build/ directory that don't exist here and there's not even a Dockerfile present in the repo (or source code)

Where does the actual 6.x.0 version number/changelog come from, if not from a commit in this repo? Is versioning driven by something outside master (a build step, a separate internal repo)?

If someone wanted to contribute to this project it would not be very easy to see whats changing between releases (and why.)

[zshall]

Sorry for the confusion! Versions 2 and up haven’t had the source released yet; all the new versions after v1 are freeware currently. The docker image and releases are all tracked from a repo on my LAN which runs off of a local CI stack. All of which would need significant cleanup to maintain history and modification so that it could work within GitHub actions to be released publicly. When I started version 2 it was an exercise in learning new tech stacks, but over the years this project became my main hobby. I’m trying to make the program as feature complete as I can first and to open up a robust API for 3rd party mods but also trying to decide on the best license to use; I’m leaning towards keeping MIT to keep it simple but I want to do it the right way and the more I read about open source and licensing the more complicated it seems to get.

I would like to eventually open it up again to contributions but in a way that keeps it fun for me to work on. Until then it’s essentially a one-person operation (though I rely on lots of other people’s work to make it all work: https://docs.tvs.gcpw.art/credits-and-thanks/ ) , but I do take feature requests and listen to feedback.