On 25 March 2015 at 09:28, Marko Lindqvist wrote:
>
> Please let me know soon if some items should be added to 2.6 status.
One thing I would hear opinions about is related to patch #5340
currently targeted to 2.6.0 - or more generally bug #22234 "Scenarios
could be compatible with more than one
On 7 December 2014 at 12:04, Marko Lindqvist wrote:
> It's less than a month to S2_6 branching 02-Jan-15.
>
> My S2_6 status page is http://freeciv.wikia.com/wiki/User:Cazfi/2.6_Status
Next step with S2_6 is making a "alpha0" Windows Installer build, to
give also windows users (for whom compilin
On 7 December 2014 at 12:04, Marko Lindqvist wrote:
> It's less than a month to S2_6 branching 02-Jan-15.
>
> My S2_6 status page is http://freeciv.wikia.com/wiki/User:Cazfi/2.6_Status
> There are new items about gtk3-client zoom feature and headers usable
> from external projects since the last s
It's less than a month to S2_6 branching 02-Jan-15.
My S2_6 status page is http://freeciv.wikia.com/wiki/User:Cazfi/2.6_Status
There are new items about gtk3-client zoom feature and headers usable
from external projects since the last status mail.
There's already also S3_0 status page
http://free
On 10/3/14, Marko Lindqvist wrote:
> On 20 August 2014 15:28, Sveinung Kvilhaugsvik
> wrote:
>> Generalized action enablers
>> Current status: All spy actions are controlled by generalized action
>> enablers. Most requirements to enable the spy actions live in the
>> ruleset. Some rough edges rem
2014-08-20 14:28 GMT+02:00 Sveinung Kvilhaugsvik <
sveinun...@users.sourceforge.net>:
> Simplify writing a Freeciv client (Freeciv web, client side AI, etc)
> that isn't written in C
> What I have done until now (mostly network protocol simplifications)
> is small, independent stuff that don't nee
> replies to this email from others telling where their features are going
> would be welcome
I think this should cover it.
Generalized action enablers
Current status: All spy actions are controlled by generalized action
enablers. Most requirements to enable the spy actions live in the
ruleset. S
We now consider 02-Jan-15, so far only placeholder in task #7804, now target
for S2_6 branching.
The idea is the same as we had with early S2_5 branching. It's not necessary
to stop all feature development for 2.6 as soon as it branches, but
the difference
between early S2_6 and trunk is only that