Use tags and GitHub releases for packages (vip files) #34
Description
VIP / Artifact Handling
I want to test AF OS last packages. I have to admit that it's complicated for me to find out which package to install. I didn't read all the AF open source track on AF Guild discord, I guess I will find the info here...
On the other hand, I'm a bit surprised to find VIP package into source code repository. I usually do not version build results (exe, installer, vip, nipkg, ...) as long as I can clearly identify the source code used to get that build (usually a commit, or better, a tag).
Quick and easy improvement: use git tags + GitHub Releases
I think it could be great to use git tags plus associated GitHub release to make clear what is the last available release.
I suggest two steps to slightly change the way of doing things on AF OS repo :
- For future releases, create a tag of the repo on the commit that allow you to build a package (vip).
Tag naming convention has to be clearly defined (version of the package - it can be an alpha, beta, etc.).
Finally create a GitHub Release, linked to that tag and attach the built VIP files. - For existing releases (if relevant), identify the commits used to create the existing builds, make tags on these commits, create releases linked to that tags, and finally remove and do not version anymore the vip files (*.vip in .gitignore)
Doing so, you are also preparing the job for a potential CI process: you may want start the build process when a tag is pushed to GitHub for instance. And let it build on a dedicated build machine (can't say anymore "that works on my computer, haha").