> [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 on
All:
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.
Also Stian, it seems like the auto release script is a bit too active. It
seems to overr
This is excellent news!!
The nightly (weekly) releases seem to have helped make it more readily
available, they've seen about 500 downloads on those binary releases since
I activated it in Sept/Oct.
David
On Thu, Jan 4, 2018 at 8:08 PM Michael T. Pope wrote:
> On Thu, 14 Dec 2017 18:58:47 +103
On Thu, 14 Dec 2017 18:58:47 +1030
"Michael T. Pope" wrote:
> Very serious, alpha-release blocking:
> BR#3121 Cant attack shipt
> Desynchronization. Must fix, working on catching it now.
Marcin came through with a test case, and I am hopeful this is now fixed.
Hooray!
I have been
Here is the current bug update, with some progress. I am hammering the
top bug hard ATM. Reproducible test cases for the next three would be most
welcome. Next most useful would be fix-confirmations.
Very serious, alpha-release blocking:
BR#3121 Cant attack shipt
Desynchronization.
Hi everyone,
A new nightly release (with binaries) has been released today that contains
all of these code changes and fixes.
Download a package here: https://github.com/FreeCol/freecol/releases
Let us know if you experience any issues and as usual, report any bugs you
find.
Thanks!
David
On Fr
On Thu, 28 Sep 2017 19:46:00 +0930
"Michael T. Pope" wrote:
> OTOH bad news on stability/release-worthiness. I am having trouble
> starting new games. There is more weirdness with UpdateMessage still.
The breakage turned out to be pretty severe, and has resulted in a bunch
of new code, which is
Hi Mike,
I see you've been working on the issues of starting new games.
Is there any way that we/I can help?
David
On Thu, Sep 28, 2017 at 1:41 PM Michael T. Pope wrote:
> On Wed, 27 Sep 2017 19:05:16 +0930
> "Michael T. Pope" wrote:
> > On Tue, 26 Sep 2017 22:20:55 +
> > David Lewis wro
On Wed, 27 Sep 2017 19:05:16 +0930
"Michael T. Pope" wrote:
> On Tue, 26 Sep 2017 22:20:55 +
> David Lewis wrote:
> > I finally managed to reproduce the server connection issue.
Added a better fallback for host resolution in git.b578952. Please test.
OTOH bad news on stability/release-wort
On Tue, 26 Sep 2017 22:20:55 +
David Lewis wrote:
> I finally managed to reproduce the server connection issue. I was going to
> update the ticket, but SourceForge is down currently.
> This weekend while I was out of town, I booted up my computer with no Wifi
> connection and encountered the i
That's fantastic news!! I've been trying to get players to download some of
the nightly releases so that we could get more eyes on the binary releases.
The good news is that it seems I've sorted out the remaining issues there
that were blocking the release as well, so we're pretty well ready.
I fi
On Fri, 22 Sep 2017 07:54:42 +0930
"Michael T. Pope" wrote:
> Ordinary single unit animation should be more reliable now, but the full
> complexity of the problem is not completely fixed yet (try a complex game
> and hit the "execute orders" command to see the carnage), but the main
> thing blocki
> The other problem is that move animation is racing.
A big piece of leftover work from the DOM-removal is needed to fix this.
Pity, I was hoping to be able to leave it out. I just committed the main
parts (git.7a6f8f7, git.549b504). My overnight tests are looking good
with these changes, but th
On Sun, 17 Sep 2017 04:50:37 +
David Lewis wrote:
> 3062 I've not seen since I reported it. Although I'm less worried about
> that bug because it doesn't block the game.
Point taken, but it is indicative of game corruption, which is serious.
Cheers,
Mike Pope
pgphJBaBJ58QJ.pgp
Description:
3090 is concerning to me and I hope someone else runs into it so that we
can get some visibility. It might have something to do with the WiFi
network I was on that week. I've not been able to reproduce it since.
3062 I've not seen since I reported it. Although I'm less worried about
that bug becau
On Sat, 12 Aug 2017 10:20:47 +0930
"Michael T. Pope" wrote:
> Updating the blocker status since last round:
Updating again. IMHO there are two hard blockers ATM/
> BR#3083 Y Rapid Go-To Wont Wait
This is still broken in a test game I have. Working on it.
The other problem is that move ani
You lost me on the Brown Paper Bag release... what is/was that? I'm
completely unfamiliar with the direct downloads vs intermediate releases,
educate me?
I think we could (in the future) have decent version handling. We're at
beta being anything 0.y.z, so technically there is no RC release needed
On Fri, 11 Aug 2017 16:36:20 +
David Lewis wrote:
> I'd love to do a pre-0.12 release to do just that... but since this is
> still beta, 0.12.0 **is** the pre-release to 1.0.0 anyway. That's why my
> opinion/vote would be to just go for it -- creating the 0.12.0 release
> soonish, knowing ther
I can't figure out how to move a ticket from one tracker to another... is
this possible, or is it done manually?
BTW, no problem play-testing 3083, thought it would be awesome if we had
several individuals look at it after the fix.
-- David
On Fri, Aug 11, 2017 at 5:51 PM Michael T. Pope wrote:
Updating the blocker status since last round:
On Sat, 29 Jul 2017 13:04:47 +0930
"Michael T. Pope" wrote:
>...
> BR#3058 Y Custom difficulty fun, working on this now
> BR#3060 N Wagon train requirement, waiting for reproducible case
> BR#3061 ? Requirements panel crash, unclear
> BR#3062 Y
I agree with David. A release is a good idea even if it requires a
"brown paper bag" release immediately when some show stopper pops up. We
clearly need bug reports against the current codebase rather than the
last released version. Given the extensive renovations since the last
0.11.x release,
*> All true. However we have had a few "Oh shit" releases, where we putout
version N only to have to put out N+1 almost immediately to fix aglaring
bug. *
In an ideal situation, and I'd say once FreeCol is considered out of beta
(stable), we'd have release candidates where this sort of thing woul
On Thu, 10 Aug 2017 17:57:26 +
David Lewis wrote:
> I agree that 3083 should be fixed before release, that is currently the
> biggest annoyance in the game.
Its now top of the list. However, once fixed, its going to need
play testing as there are a lot of cases.
> Part of the reason I'd li
For BR#3062, I don't know if we'll be able to solve that before release.
I've been trying to reproduce without success. Added a comment to the
ticket for more info.
I agree that 3083 should be fixed before release, that is currently the
biggest annoyance in the game.
If there are objections and/o
On Thu, 10 Aug 2017 01:43:56 +
David Lewis wrote:
> There's a new bug report where the version attribute isn't set in the
> savegame file and thus doesn't load the unit-change-types correctly,
> causing an NPE on selecting a teacher. That's the only one I've found thus
> far.
Will check. I a
There's a new bug report where the version attribute isn't set in the
savegame file and thus doesn't load the unit-change-types correctly,
causing an NPE on selecting a teacher. That's the only one I've found thus
far.
I'd like to set a goal of releasing by Tuesday, August 22nd if there are no
maj
On Sat, 29 Jul 2017 13:04:47 +0930
"Michael T. Pope" wrote:
> I also have a blocker due to some of my old (0.11.*) games crashing
> on load. Should have this done soon.
This is now resolved. I can not find any 0.11.x games of mine or attached
to current bugs that has any loading problems. Now
David,
I believe the official reason for the minor version bump is because version
0.12.0 games will no longer be to read version 0.10.x games. A conversion
would require 0.10.x save file be loaded in 011.x and then re-saved and
then loaded in 0.12.0 (or later)
BTW: Mike thanks for all your hard
rtime
Gesendet: Samstag, 29. Juli 2017 um 17:06 Uhr
Von: "David Lewis"
An: "Michael T. Pope" , freecol-developers@lists.sourceforge.net
Betreff: Re: [Freecol-developers] 0.12.0
I'm curious why the 0.11.7 wiki page rather than it being 0.12.0?
David
On Fri, Jul 28, 201
I'm curious why the 0.11.7 wiki page rather than it being 0.12.0?
David
On Fri, Jul 28, 2017, 8:35 PM Michael T. Pope wrote:
> Plenty of bug reporting activity, especially from David Lewis. Keep them
> coming, they are better fixed now than any other time. I went through the
> list a bit more
Plenty of bug reporting activity, especially from David Lewis. Keep them
coming, they are better fixed now than any other time. I went through the
list a bit more thoroughly. Still have not had much of a chance to play
test myself, alas.
Open bugs since 0.11.6-release
Bug# Blocker?
BR#2936
Been playing and testing each of the commits, and there are some bugs and
quirks here and there that I've found, but so far nothing major and
blocking that I've seen thus far. I'm still trying some different
configurations to ensure there is nothing major, but would like to get
0.12.0 out pretty so
Finally, the DOM-removal is done, and I have no recent sightings of
BR#2925. These were the major release blocking problems, so we should
now be testing/stabilizing in expectation of the 0.12.0 release. I
have several things that need play-testing, having just destabilized
diplomacy with a fix re
I see, thank you for explanation. :)
Fiisch
2017-02-12 9:07 GMT+01:00 Michael T. Pope :
> On Thu, 9 Feb 2017 15:47:55 +0100
> Petr Fišer wrote:
>> is basically just about FreeCol not being able to upgrade savegames
>> from 0.10.x and older,
>
> FreeCol 0.12.0, which will be the next release, will
On Thu, 9 Feb 2017 15:47:55 +0100
Petr Fišer wrote:
> is basically just about FreeCol not being able to upgrade savegames
> from 0.10.x and older,
FreeCol 0.12.0, which will be the next release, will not be able to read
0.10.x format savegames. This is normal for releases with (semi-)major
numbe
Hi,
So if I understand correctly, then the note
"wintertime and I have both hit places where the 0.10.x compatibility
code is impeding
progress, so it is time to drop support for the 0.10 format save games and
protocol..."
is basically just about FreeCol not being able to upgrade savegames
from 0.1
On Wed, 8 Feb 2017 18:54:22 +0100
win...@genial.ms wrote:
> FreeCol 0.11.x is the tool to upgrade 0.10.x games. You just need to load and
> save again.
Exactly, and that is the longstanding intent.
> I'm just not sure how far it goes and if its just savegames or also mapfiles.
> I guess, some
d bug,
but would like to get confirmation on that.
> Gesendet: Mittwoch, 08. Februar 2017 um 17:53 Uhr
> Von: "Petr Fišer"
> An: "Michael T. Pope"
> Cc: "FreeCol Developers"
> Betreff: Re: [Freecol-developers] 0.12.0
>
> Hi,
> Your note abou
Hi,
Your note about breaking save games got me thinking - what about a
tool/feature for upgrading savegames to current *release* versions.
It is still a bit clunky but at least people will not lose their saved games.
Of course this means some development work and the overall benefit may
not be wort
Somewhat reluctantly I have concluded we are going to need to forgo 0.11.7
and bump the (semi-)major version number for the next release. wintertime
and I have both hit places where the 0.10.x compatibility code is impeding
progress, so it is time to drop support for the 0.10 format save games and
40 matches
Mail list logo
