Hi, * We are now using https for freecol.org * The master branch on SF.net is automatically mirrored to GitHub on every push (using a server hook). * GitHub Actions is used for building on every push, and making the packages available on the workflow in a single ZIP file (see [1]).
I can automate the release, but there would be a lot of releases if we do it automatically for every push. Some suggestions: 1. We can have the files (separately) available on the workflow. The testers would then always get the latest build. The drawback being all files are wrapped in a zip-file anyway -- so, for example, the jar file would be inside a zip file. 2. We can trigger the release process manually a. ...by making changes to a file (like "CHANGELOG.md" or "TESTRELEASE.md"). The entire text in that file can be used as release notes. b. ...by publishing a release from GitHub.com (the files would be automatically included). c. ...by manually starting the workflow from GitHub.com. What would you like as a solution? ...or should I just pick the easiest one (no. 1)? Best wishes, Stian Grenborgen [1] https://github.com/FreeCol/freecol/actions/runs/2235535445 _______________________________________________ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
