[Freecol-developers] FreeCol 0.11.5

[Michael T. Pope]

FreeCol 0.11.5 has been released with one critical bug fix from the
withdrawn 0.11.4. All 0.10.x and 0.11.x games should continue to work
with 0.11.5, with the exception of games generated with 0.11.4 which
are badly broken.

For more details on the changes since 0.11.3, see
the [release notes](https://sourceforge.net/p/freecol/wiki/0.11.5%20Release%20Notes/).

We this time you get to enjoy the new FreeCol release. Onward to 1.0.

The FreeCol Team

[Caleb Williams]

Looks like the website is still out of date.

Thanks,

Caleb

[Michael T. Pope]

On Mon, 3 Aug 2015 19:30:19 -0500
Caleb Williams <***@gmail.com> wrote:
> Looks like the website is still out of date.

Looks OK from here. Which page/s?

Cheers,
Mike Pope

[Michael T. Pope]

On Tue, 4 Aug 2015 18:46:10 +0930
"Michael T. Pope" <***@computer.org> wrote:
> On Mon, 3 Aug 2015 19:30:19 -0500
> Caleb Williams <***@gmail.com> wrote:
> > Looks like the website is still out of date.
>
> Looks OK from here. Which page/s?

I kicked out the Joomla tags with a one-liner and used those changes to
trigger a big push, hopefully catching what was bothering you.

Cheers,
Mike Pope

[Caleb Williams]

How does that script work? I know next to nothing about Shell scripts. I do
know the site was up to date when I visited later.

Caleb
On Aug 4, 2015 4:16 AM, "Michael T. Pope" <***@computer.org> wrote:

> On Mon, 3 Aug 2015 19:30:19 -0500
> Caleb Williams <***@gmail.com> wrote:
> > Looks like the website is still out of date.
>
> Looks OK from here. Which page/s?
>
> Cheers,
> Mike Pope
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Freecol-developers mailing list
> Freecol-***@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freecol-developers
>
>

[Michael T. Pope]

On Tue, 4 Aug 2015 07:50:47 -0500
Caleb Williams <***@gmail.com> wrote:
> How does that script work?

Just uses git to find the commit that last modified the www.freecol.org
directory, extracts the list of modified files from that commit, and
uses sftp to upload those from our directory to the corresponding
directory/s on the website.

> I know next to nothing about Shell scripts. I do
> know the site was up to date when I visited later.

So it could have been caching somewhere, or slowness at sourceforge, or
what I did worked. We are unlikely to ever know.

Cheers,
Mike Pope

[Caleb Williams]

It would appear that the /templates/freecol/css/template_css.css isn't
being updated. I've made a few changes that are required to continue with
the cleanup of the site.

Thanks for cleaning up the Joomla generator tag too, btw.

Best,

--
*Caleb R. Williams*

[w***@genial.ms]

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

[Caleb Williams]

I will take a look at both of those. Do you happen to know when both of
those went into effect? (Release version, that is.)

Best,

Caleb
On Aug 23, 2015 1:26 AM, <***@genial.ms> wrote:

> Hi,
>
> on the download page is a weird note about missing sound files.
> I think it is way outdated, as I never saw such message.
> The second note is also outdated, as --windowed is now default.
>
>
> Greetings,
>
> wintertime
>
>
> *Gesendet:* Sonntag, 23. August 2015 um 03:05 Uhr
> *Von:* "Caleb Williams" <***@gmail.com>
> *An:* "FreeCol Developers" <freecol-***@lists.sourceforge.net>
> *Betreff:* Re: [Freecol-developers] FreeCol 0.11.5
> It would appear that the /templates/freecol/css/template_css.css isn't
> being updated. I've made a few changes that are required to continue with
> the cleanup of the site.
>
> Thanks for cleaning up the Joomla generator tag too, btw.
>
> Best,
>
> --
> *Caleb R. Williams*
>
>

[w***@genial.ms]

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

[Caleb Williams]

Removed the notes and added a notice that FreeCol will require Java 1.8
with the next release.

--
*Caleb R. Williams*

[w***@genial.ms]

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

[Caleb Williams]

I was under the impression 1.8 would be the version going forward from the
discussions on the mailing list. Obviously that could be incorrect. I guess
we will need some direction from Mike. Those changes can be reverted of
course too.

--
*Caleb R. Williams*

[Michael T. Pope]

On Sun, 23 Aug 2015 18:33:16 +0200
***@genial.ms wrote:
> I hope we will, but afaik we have not yet decided if thats in next release or later?

I think 1.7 going unsupported is enough to encourage us to move quickly.
When we last discussed this I wanted to check the OS X situation before
deciding. I have since done so, finding that 1.8 is the default download,
and 0.11.5 builds and runs fine if built with it on an oldish mac I have
access to. The Debian world were the only other concern, but I think the
presence of 1.8 in -unstable is good enough there. I do like Debian, but
they are doing us no favours by continuing to package 0.10.7 (even in
-unstable), so I am disinclined to let them determine our policy. So, I
think Caleb has made the right edit:-). 1.8 for FreeCol-next-release it
is, and belated apologies to William Astle for the jogg/jorbis problem.

> Java 1.7 is effectively dead, as you can not download it for testing anymore without having
> an Oracle account, which requires info like the name of company you represent...

That sounds like Oracle alright.

Cheers,
Mike Pope

[William Astle]

On 2015-08-26 01:19, Michael T. Pope wrote:
> 1.8 for FreeCol-next-release it
> is, and belated apologies to William Astle for the jogg/jorbis problem.

For what it's worth, it's the sort of thing you should expect if you use
a development branch of a project. And the solution was easy enough:
install Java 1.8.

I agree that letting what Debian packages determine development policy
is a bad idea so regardless of any trouble I had, I agree that requiring
1.8 is the right call.

Quite a lot of what Debian packages is rather old. It gets worse when
you run into long term support releases of Debian derivatives. It's not
just limited to Java. I've had issues with a lot of packages over time
simply due to the ancient version Debian or one of its derivatives
decided to package. The allergy to upgrading anything other than a minor
patch level during a release cycle (regardless of upstream support) for
a lot of distributions doesn't help either.

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