[Freecol-developers] TIme again to stablize

[Michael T. Pope]

BR#2906 (now fixed) turned up the sad fact that 0.11.5 does not let you
directly found a colony on native land. This is a fairly major loss of
functionality, so I think we should stabilize for a release. There have
been a few changes which I would have preferred to let settle, but OTOH,
the release procedure is now relatively automated so the barrier to making
further bugfix releases is lower. So here is your chance to nominate
release blocker problems. For my part, I would really like to fix the
diplomacy issues (BR#2879,2880,2891).

Cheers,
Mike Pope

[w***@genial.ms]

Hi,

> Gesendet: Freitag, 04. September 2015 um 12:39 Uhr
> Von: "Michael T. Pope" <***@computer.org>
>
> BR#2906 (now fixed) turned up the sad fact that 0.11.5 does not let you
> directly found a colony on native land. This is a fairly major loss of
> functionality, so I think we should stabilize for a release.

Had you tried if all other methods of acquiring land were affected?
If you could still pretend to build a road or something or grab tiles inside
the colony its an annoying bug, but if nothing worked it raises to a complete
blocker. The urgency of release would raise in that case, too.

> There have
> been a few changes which I would have preferred to let settle, but OTOH,
> the release procedure is now relatively automated so the barrier to making
> further bugfix releases is lower. So here is your chance to nominate
> release blocker problems. For my part, I would really like to fix the
> diplomacy issues (BR#2879,2880,2891).

I guess the changes have not been very destructive, so we should be in pretty
good shape still.
You told the translators already that a release might come soon? Last update
had been before 11.4 and there have been a few message changes since?
How soon do you think the realease would be anyway?

I took a look at the bug list and BR#2876 is the one i feel got the potential
of causing release breakage again. What is the current status of it?

Besides that, the developer.pdf is packaged now. Can you put an item on your
release checklist to doublecheck its correctly included in all compiled packages?
It may be nice to have a startmenu shortcut and similar added for it?


Greetings,

wintertime

------------------------------------------------------------------------------

[Michael T. Pope]

On Sat, 5 Sep 2015 11:05:43 +0200
***@genial.ms wrote:
> Had you tried if all other methods of acquiring land were affected?
> If you could still pretend to build a road...

I am sure that would work, and it is nice to have a workaround, but the
bug remains serious enough IMHO, workaround or no.

> I guess the changes have not been very destructive, so we should be in pretty
> good shape still.

Its looking reasonable. One diplomacy bug is fixed and I am having
trouble reproducing the other, so I intend play testing until something
else arises. I have some trivial Java 8 simplifications still in the
patch queue, but everything else is post-release material now.

> You told the translators already that a release might come soon?

No. They work when they can. We can expect no more.

> How soon do you think the realease would be anyway?

Er, "soon"? Obviously I want to do some play testing... no earlier than
the weekend after next at least.

> I took a look at the bug list and BR#2876 is the one i feel got the potential
> of causing release breakage again. What is the current status of it?

The crash is fixed, and on the way several options are now sanity tested,
so that report definitely improved robustness. Following on there is a
bunch of enhancements to the option dialog/s that we discussed a while
back, which is about 3rd on my todo list, but post-release material now.
What remains broken is the missing message about the language change, as
described in the last paragraph of my last comment there. Not a
show stopper, but annoying nonetheless. Feel free to look into it if you
like.

> Besides that, the developer.pdf is packaged now. Can you put an item on your
> release checklist to doublecheck its correctly included in all compiled packages?

Done.

> It may be nice to have a startmenu shortcut and similar added for it?

How about a reference on the AboutPanel, like the user manual?

Cheers,
Mike Pope

[LoneVVolf]

On 08-09-15 13:29, Michael T. Pope wrote:
>> You told the translators already that a release might come soon?
> No. They work when they can. We can expect no more.

http://sourceforge.net/p/freecol/git/ci/61b1fc018cbdd2958a40bcd333a63f4e5a30165c/

Looks like Translators have caught up.

LVV

[w***@genial.ms]

Hi,

> Gesendet: Dienstag, 08. September 2015 um 13:29 Uhr
> Von: "Michael T. Pope" <***@computer.org>
> > Besides that, the developer.pdf is packaged now. Can you put an item on your
> > release checklist to doublecheck its correctly included in all compiled packages?
>
> Done.
>
> > It may be nice to have a startmenu shortcut and similar added for it?
>
> How about a reference on the AboutPanel, like the user manual?
>

Oddly, this is pointing to the website saying "download the manual" there,
when it should be packaged already? We might just update that website to
contain both manuals, then later change the message to say both manuals
are there?
The ingame link is non-functional for me though, it doesn't open the browser?


Greetings,

wintertime

------------------------------------------------------------------------------

[Michael T. Pope]

On Fri, 18 Sep 2015 22:10:02 +0200
***@genial.ms wrote:
> Oddly, this is pointing to the website saying "download the manual" there,
> when it should be packaged already? We might just update that website to
> contain both manuals, then later change the message to say both manuals
> are there?

That would be an improvement. IIRC the argument was that while the
manuals are packaged, we can not be 100% sure where they end up due to
variation in how distros or users arrange their file systems, whereas OTOH
a URL is more reliably under our control.

> The ingame link is non-functional for me though, it doesn't open the browser?

Confirmed, and this is weird because the other two links above it work
fine, and the URL itself works fine if entered on a browser.

Cheers,
Mike Pope

[Michael T. Pope]

On Sat, 19 Sep 2015 07:04:57 +0930
"Michael T. Pope" <***@computer.org> wrote:
> Confirmed, and this is weird because the other two links above it work
> fine, and the URL itself works fine if entered on a browser.

Doh. The fix was trivial, git.c63e5a4.

I recommend we change the manual url to a generic documentation link to
www.freecol.org/documentation and make sure all the documents are
available from there.

Cheers,
Mike Pope