> [Caleb:] > I've posted an official release on GitHub for 0.12.0. Can someone with admin > access > there upload the installers to the release? My internet here is so slow that > it wouldn't get > done for hours if I tried.
I think we should keep the official releases on SourceForge.net, and only add links to GitHub. One reason being there's no download statistics on GitHub. Other projects like Wesnoth also does the same -- only mention the release on GitHub and publish it on SourceForge.net: https://github.com/wesnoth/wesnoth/releases > [Caleb:] > Also Stian, it seems like the auto release script is a bit too active. It > seems to override > previous notes as well. I think that should be made no more frequently than > once per day. There are advantages to having the development release update every time we have a commit. Primarily, that we do not need to do anything to have an updated development build. If we were to, say, have the release update once every day -- then we should also have a method for updating the build manually so that testers can quickly verify whether an issue has been fixed or not. We have been using the nightly releases as a substitute for proper releases, but we should rather publish point (bug fix) releases more often on SF.net. There was a need for a changelog on the nightly releases as they were made rather irregularly. I don't think the development release needs a changelog now ... other than to indicate what the latest included commit is. Best wishes, Stian Grenborgen _______________________________________________ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
