URL: http://bugs.freeciv.org/Ticket/Display.html?id=39730
[wsimpson - Jeu. Oct. 11 23:03:37 2007]:
Committed S2_1 revision 13744.
Committed S2_2 revision 13745.
You forgot to change the main mandatory capability.
___
Freeciv-dev mailing list
URL: http://bugs.freeciv.org/Ticket/Display.html?id=39770
When you use the command /set timeout 60 while the game is running, the
timeout change only the next turn. The problem is that
game.info.seconds_to_phasedone doesn't change when game.info.timeout is
changed.
A callback like:
URL: http://bugs.freeciv.org/Ticket/Display.html?id=39730
You forgot to change the main mandatory capability.
In 2.1, I'm expecting that to change with a new (+2.1g) release
tomorrow. Since there's no possibility of backward compatibility,
both ReportFreezeFix and CF can go away, too.
In
On 10/12/07, William Allen Simpson [EMAIL PROTECTED] wrote:
Daniel Markstedt wrote:
Let's wait 24h before tagging, to let some final fixes go in. Between
now and final, docs need some attention too. Especially translated
docs.
Ok, cool. How long after the tag is the final release? 7
Daniel Markstedt wrote:
Let's wait 24h before tagging, to let some final fixes go in. Between
now and final, docs need some attention too. Especially translated
docs.
Ok, cool. How long after the tag is the final release? 7 days?
___
Freeciv-dev
URL: http://bugs.freeciv.org/Ticket/Display.html?id=39614
S2_1, S2_2 and trunk would need the 3 patch. S2_0 will need an
adaptation of the second one.
___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev
URL: http://bugs.freeciv.org/Ticket/Display.html?id=39614
Third step: client connection list side.
+ /cmdlevel and /cut send the username to the server, not the player
name which can be different.
+ the /cmdlevel ctrl menu item really makes it, no /cut.
Patch attached
Index:
URL: http://bugs.freeciv.org/Ticket/Display.html?id=39771
Good daytime!
As I said early, current freeciv.desktop is not proper.
Attached are freeciv-server.desktop.in and patch to freeciv.desktop.in
(and configure/Makefile.)
Changed categories, removed version, removed extension of icons
On 10/12/07, William Allen Simpson [EMAIL PROTECTED] wrote:
I'm not sure how to tag the release (do I have to checkout 1 level above
the branches?) -- Daniel can do that -- but version.in has been set.
___
Freeciv-dev mailing list
URL: http://bugs.freeciv.org/Ticket/Display.html?id=10284
On Fri, 28 Sep 2007 00:55:40 -0700 Daniel Markstedt wrote:
[evyscr - Mon Jan 23 17:17:10 2006]:
[evyscr - Sep 23 20:12:58 2004]:
It would be nice to see FAQ file in freeciv distribution, wouldn't it?
New version.
* uses
On 10/12/07, William Allen Simpson [EMAIL PROTECTED] wrote:
Assuming we're following the usual commercial release criterion,
problems that would stop the cycle now would be:
1) reproducible crashing bugs,
2) that aren't already in previous 2.0.x releases.
Anything else waits until the
Assuming we're following the usual commercial release criterion,
problems that would stop the cycle now would be:
1) reproducible crashing bugs,
2) that aren't already in previous 2.0.x releases.
Anything else waits until the next release (2.1.x or 2.2.0).
I'm presuming that we still want
URL: http://bugs.freeciv.org/Ticket/Display.html?id=39769
On Thu, 11 Oct 2007 14:44:07 -0700 Daniel Markstedt wrote:
From: Egor Vyscrebentsov evyscr
Date: Oct 12, 2007 1:05 AM
Subject: Re: [Freeciv-Dev] Freeciv Icons
To: freeciv-dev@gna.org
On Thu, 11 Oct 2007 07:51:52 +0900 Daniel
URL: http://bugs.freeciv.org/Ticket/Display.html?id=39614
Second step: notify to the clients all changes about connections:
+ new created players names when a client joins.
+ lost detached connections.
+ when a player get detached after a /remove usage.
+ when a game is loaded with /load,
William Allen Simpson wrote:
1) reproducible crashing bugs,
PR#39602, 39615.
2) that aren't already in previous 2.0.x releases.
PR#20772, 39697, 39613, 39744.
And other incomplete features...
Is it enough to have at least a week before release?
Pepeto _
You seem to have interpreted these 2 criteria as /or/, but the
usual English interpretation of *and* applies: both criteria must be
met to delay the release.
Bugs in 2.0 are *especially* not applicable. They are known and
didn't affect the current/previous release cycle. If they are
On 10/13/07, William Allen Simpson [EMAIL PROTECTED] wrote:
Pepeto _
You seem to have interpreted these 2 criteria as /or/, but the
usual English interpretation of *and* applies: both criteria must be
met to delay the release.
Bugs in 2.0 are *especially* not applicable. They are known and
17 matches
Mail list logo
