[Freecol-developers] GitHub Mirror and "Nightly" releases
Stian, et. al., The GitHub mirror was originally configured to be an automatic process. I believe it was a Travis CI hook, but at any rate when changes were made to the SF repository, the CI hook ran and pushed to GH. AFAIK, the nightly releases were also automated, probably through the same hook to Travis CI. At any rate, the CI was no longer free (due to plan changes) and quit working. Who ever set up this stuff was no longer active with the project and nobody noticed that was active since most of the stuff was done on SF. I finally removed the .yml files when I noticed that while GH attempted to run the script, it always failed due to no longer being a free service. Right now, I have created the "nightly" releases manually using *ant dist*. I then make sure GH is mirroring SF (manually). I create a pre-release tag with the results from *ant dist* and publish it. I then post on the Facebook and Discord groups (thanks Blake) that a new release is available on GH. I try to keep a handle on major fixed bugs since last nightly and add a note in the release notes. One issue with the process is it isn't consistently timed as I have to physically perform each part of the process. I also cannot generate the MacOS installer. I don't mind doing so, as the more people are playing this version the fewer are playing 0.11.6. This leads to more relevant bug reports, such as the multiplayer one. Thanks, Caleb Williams ___ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
Re: [Freecol-developers] FreeCol 1.0
Well if you guys don't call it the big 1.0 then it would be good to see the big 0.12.0 stable release finally out there. People are still downloading the ancient 0.11.6 stable release due to them thinking the nightly releases are scary mega unstable programs lol. However in their attempt to be 'safe' they end up with a super old version of the game that's missing a lot of the features the latest builds have. So whatever you call it I'll just be happy to see that old 0.11.6 build gone from all the download pages and replaced with a new stable one. As for whether it's ready to be called 1.0 that's up to you guys but I would agree that waiting until Misiulo has finished the rest of the graphics is best otherwise it looks like a bit of a unfinished jumble of 2D and 3D terrain. Also I find myself wondering whether preserving all the old 2D art stuff as a optional mod would be handy for those that don't like the new stuff when it's all done for 1.0. Speaking of mods, Mazim's finally completed his popular New Nations mod that not only adds more nations but also allows people to play 12 player Col games (which is a handy line when I'm marketing the game heh) so it would be good to finally add that into the included mods area before any such big release so people don't have to keep digging through his thread for it separately:https://sourceforge.net/p/freecol/discussion/141200/thread/658935e76f/?page=1#0a18 I already added all of Mazim's best maps from his collection into FreeCol's releases a while back so that's all good now. So yeah.. nothing else really comes to mind from me. :) Regards Blake On Friday, 22 April 2022, 01:55:52 pm ACST, Michael T. Pope wrote: On Thu, 21 Apr 2022 18:09:51 + Stian Grenborgen wrote: > We have made great progress on FreeCol since our last release, and should > make an official release rather soon. > > I think releasing the game as 1.0 will show the level of maturity our game > has reached ... and also signify the awesome new additions to the game: All this is true and great progress, but we have always said 1.0 will be fully Col1 compatible (at least in classic mode). I do not think we are there yet. A look at the WWC1D? wiki page will show that we do not even know how compatible we are:-). We *should* indeed do a release though, whatever the number it gets. It is overdue. I was not pushing hard there lately as (apart from the usual time crunches) the worst blocker bug was the total breakage (some self-inflicted:-P) of the TradeRouteInputPanel. Which just got fixed this week, bravo Stian. The next worst one I know is the queue of AI ships (BR#3228) which I hope to look at one the weekend (long weekend in .au, hooray), but letting AI fail block release is a bad idea. However I probably should do a quick review of the state of the bug list to see if we have other bad enough bugs to be considered release blockers. I will try to do the review this evening. Cheers, Mike Pope ___ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers ___ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
Re: [Freecol-developers] FreeCol 1.0
On Fri, 22 Apr 2022 13:54:05 +0930 "Michael T. Pope" wrote: > I will try to do the review this evening. How about that, we are in pretty good shape. I have looked through the bugs back to 0.11.6, and found only one that I consider release blocking, which is Marcin's REF immediate surrender problem in #3246. So that is now my high priority weekend job. The AI ship fail (3247 == 3228) is "would be nice". Perhaps I am too used to the AI failing. Next on the list. There are quite a few bugs stuck in a needinfo state, if anyone wants to take a shot at improving the release quality: 3243: Gameplay bugs 3229: modifications reset after save 3225: too much lumber 3222: Colony population displayed incorrectly when spying 3217: Colony gains production bonus incorrectly 3188: Cannot establish mission w/ captured missionary? 3183: Labor Advisor window got a glitch. (freecol-nightly-2020-02-27) 3167: Ship cannot return from Europe 3162: Error "The server can not do that." when trying to haggle 3155: Wrong Starting Units 3151: Royal expeditionary land forces not increasing 3149: H - go to city command failure 3146: Suffered a big savegame corruption error 3134: User Interface Issues 3081: Master Gunsmith Doesnt have connections 3062: Map Explored Regions Error 3035: Broken key mapping for closing panels 3025: Incorrect saves (map editor) 3012: Turn report exclusions not working I suspect several of these are actually fixed, or moot, or both. Finally I have some graphics BRs for Stian:-). Are #3216 and #3209 fixed? And did your recent work include fixing the river selection panel #2926? Cheers, Mike Pope pgpSTgKIi0edr.pgp Description: OpenPGP digital signature ___ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
