Re: [Freeciv-Dev] About S3_0 branching

2017-01-01 Thread Marko Lindqvist
 Branching has been done. Both TRUNK and S3_0 are open to regular commits.


 - ML


On 30 December 2016 at 13:05, Marko Lindqvist  wrote:
>> On 7 October 2016 at 04:18, Marko Lindqvist  wrote:
>>>  S3_0 branching has been agreed to happen 02-Jan-17.
>
>  About three days to go. When opening new tickets (or touching old
> ones) please remember that anything to be committed to TRUNK after
> branching needs to have 3.1.0 in its list of target releases.
>
>
>  - ML

___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev


Re: [Freeciv-Dev] About S3_0 branching

2016-12-30 Thread Marko Lindqvist
> On 7 October 2016 at 04:18, Marko Lindqvist  wrote:
>>  S3_0 branching has been agreed to happen 02-Jan-17.

 About three days to go. When opening new tickets (or touching old
ones) please remember that anything to be committed to TRUNK after
branching needs to have 3.1.0 in its list of target releases.


 - ML

___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev


Re: [Freeciv-Dev] About S3_0 branching

2016-12-18 Thread Marko Lindqvist
 Reminder that S3_0 branching is in two weeks.


On 7 October 2016 at 04:18, Marko Lindqvist  wrote:
>  S3_0 branching has been agreed to happen 02-Jan-17.


 - ML

___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev


Re: [Freeciv-Dev] About S3_0 branching

2016-10-06 Thread Marko Lindqvist
 S3_0 branching has been agreed to happen 02-Jan-17.

 Translation statistics from current branches are in the end of this
email. Po-files in
http://download.gna.org/freeciv/packages/windows/testing/cazfi/translations/
have just been updated against latest translatable strings.


On 12 September 2016 at 21:50, Marko Lindqvist  wrote:
> - S2_5 is receiving only occasional commits. 2.5.6 should be released
> so that it makes
> it to Debian Stretch before freeze - late this year or in the
> beginning of January.
> It's possible that it will be the last release from S2_5.
>
> - S2_6 is stable, and most things getting committed to trunk are not
> committed there.
>
> - We are already piling up things that would make more sense to get
> committed early
> in 3.1 cycle than close-to-branching to 3.0.
>
> - One conclusion in the earlier freeciv-2.7 speculation was that S3_0 would 
> get
> branched soon, to cut out need for another version while waiting 3.0.
>
>
> With these points in mind, I'm proposing setting 02-Jan-17 as the S3_0
> branching date.
> That is 24 months after S2_6 branching. The branching date is not a
> date after which
> no new features can be started, but rather just an option to have some
> committed new
> features targeted to 3.1 (trunk-only). However, I think S3_0 will be a
> bit different
> from S2_6 in that latter is about last freeciv-2 release, and as such we've 
> been
> trying to tie odd ends more than usually. In S3_0 I expect us to be
> more likely to
> just postpone things to 3.1, especially if they seem like too
> distruptive change given
> where we go in the 3.0 cycle.
>
> How does this sound, especially to active developers who have certain
> features to include to 3.0 in mind?
>
>
>  - ML


 Stats by branch and domain

S2_5 freeciv
--
ar 34%
bg 21%
ca 100%
cs 40%
da 70%
de 98%
el 31%
en_GB 100%
eo 38%
es 100%
et 40%
fa 22%
fi 100%
fr 100%
ga 45%
gd 82%
he 23%
hu 26%
id 43%
it 61%
ja 93%
ko 50%
lt 37%
nb 34%
nl 61%
pl 95%
pt_BR 57%
pt 24%
ro 36%
ru 100%
sr 29%
sv 50%
tr 41%
uk 91%
zh_CN 34%
zh_TW 26%

S2_5 nations
--
ar 7%
bg 23%
ca 100%
cs 10%
da 59%
de 87%
el 8%
en_GB 100%
eo 13%
es 100%
et 11%
fa 9%
fi 91%
fr 100%
ga 59%
gd 83%
he 7%
hu 5%
id 50%
it 19%
ja 95%
ko 12%
lt 14%
nb 5%
nl 51%
pl 99%
pt_BR 19%
pt 3%
ro 6%
ru 100%
sr 7%
sv 16%
tr 9%
uk 43%
zh_CN 9%
zh_TW 37%

S2_6 freeciv
--
ar 30%
bg 19%
ca 89%
cs 35%
da 62%
de 85%
el 27%
en_GB 86%
eo 34%
es 87%
et 35%
fa 20%
fi 98%
fr 87%
ga 40%
gd 73%
he 20%
hu 23%
id 38%
it 53%
ja 81%
ko 44%
lt 32%
nb 30%
nl 53%
pl 89%
pt_BR 50%
pt 22%
ro 32%
ru 98%
sr 26%
sv 44%
tr 36%
uk 56%
zh_CN 30%
zh_TW 24%

S2_6 nations
--
ar 7%
bg 23%
ca 97%
cs 10%
da 58%
de 85%
el 8%
en_GB 97%
eo 13%
es 97%
et 11%
fa 9%
fi 89%
fr 97%
ga 58%
gd 81%
he 7%
hu 5%
id 49%
it 19%
ja 93%
ko 12%
lt 14%
nb 5%
nl 50%
pl 97%
pt_BR 19%
pt 3%
ro 6%
ru 97%
sr 7%
sv 16%
tr 9%
uk 43%
zh_CN 9%
zh_TW 36%

S2_6 ruledit
--
ar 3%
bg 1%
ca 100%
cs 4%
da 4%
de 11%
el 3%
en_GB 49%
eo 4%
es 15%
et 4%
fa 1%
fi 100%
fr 68%
ga 12%
gd 11%
he 1%
hu 3%
id 7%
it 4%
ja 14%
ko 1%
lt 4%
nb 3%
nl 7%
pl 65%
pt_BR 4%
pt 3%
ro 3%
ru 100%
sr 1%
sv 4%
tr 3%
uk 4%
zh_CN 3%
zh_TW 68%

TRUNK core
--
ar 26%
bg 17%
ca 75%
cs 30%
da 55%
de 75%
el 25%
en_GB 76%
eo 29%
es 77%
et 30%
fa 18%
fi 90%
fr 91%
ga 36%
gd 64%
he 17%
hu 20%
id 34%
it 47%
ja 72%
ko 40%
lt 28%
nb 26%
nl 47%
pl 82%
pt_BR 44%
pt 18%
ro 27%
ru 79%
sr 24%
sv 38%
tr 31%
uk 50%
zh_CN 26%
zh_TW 22%

TRUNK nations
--
ar 7%
bg 23%
ca 97%
cs 10%
da 58%
de 85%
el 8%
en_GB 97%
eo 13%
es 97%
et 11%
fa 9%
fi 89%
fr 97%
ga 58%
gd 81%
he 7%
hu 5%
id 49%
it 19%
ja 93%
ko 12%
lt 14%
nb 5%
nl 50%
pl 97%
pt_BR 19%
pt 3%
ro 6%
ru 97%
sr 7%
sv 16%
tr 9%
uk 43%
zh_CN 9%
zh_TW 36%

TRUNK ruledit
--
ar 2%
bg 1%
ca 32%
cs 3%
da 3%
de 8%
el 2%
en_GB 38%
eo 3%
es 12%
et 3%
fa 1%
fi 90%
fr 51%
ga 9%
gd 8%
he 1%
hu 2%
id 6%
it 3%
ja 11%
ko 1%
lt 3%
nb 2%
nl 6%
pl 50%
pt_BR 3%
pt 2%
ro 2%
ru 53%
sr 1%
sv 3%
tr 2%
uk 3%
zh_CN 2%
zh_TW 53%



 - ML

___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev


Re: [Freeciv-Dev] About S3_0 branching

2016-09-16 Thread Sveinung Kvilhaugsvik
02-Jan-17 sounds OK to me.

___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev


[Freeciv-Dev] About S3_0 branching

2016-09-12 Thread Marko Lindqvist
- S2_5 is receiving only occasional commits. 2.5.6 should be released
so that it makes
it to Debian Stretch before freeze - late this year or in the
beginning of January.
It's possible that it will be the last release from S2_5.

- S2_6 is stable, and most things getting committed to trunk are not
committed there.

- We are already piling up things that would make more sense to get
committed early
in 3.1 cycle than close-to-branching to 3.0.

- One conclusion in the earlier freeciv-2.7 speculation was that S3_0 would get
branched soon, to cut out need for another version while waiting 3.0.


With these points in mind, I'm proposing setting 02-Jan-17 as the S3_0
branching date.
That is 24 months after S2_6 branching. The branching date is not a
date after which
no new features can be started, but rather just an option to have some
committed new
features targeted to 3.1 (trunk-only). However, I think S3_0 will be a
bit different
from S2_6 in that latter is about last freeciv-2 release, and as such we've been
trying to tie odd ends more than usually. In S3_0 I expect us to be
more likely to
just postpone things to 3.1, especially if they seem like too
distruptive change given
where we go in the 3.0 cycle.

How does this sound, especially to active developers who have certain
features to include to 3.0 in mind?


 - ML

___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev