released 4.6.1

[Arun Persaud]

Hi

just uploaded the 4.6.1 tarball :) Let's start advertising ;)
I will email the FICS people.

HGM: can you handle the savannah news item and other newsgroups?

Arun

[h.g.muller]

I am very sorry, but it seems I made a major foul-up this time.

One of the latest patches I made breaks XBoard very badly for playing
engine-engine games in a variant. The test I added to check if the second
engine supports the variant is made before that engine is actually started
(and has told XBoard what variants it plays). So the test always fails,
and XBoard refuses to switch to two-machines mode.
   There is a work-around, which is to make sure the second engine has
already been started, e.g. by opening Engine #2 Settings, or playing a game
in variant normal, before using TwoMachines mode. But this is not possible
in engine matches or tournaments. I must have done one of these things
when testing the feature (probably first playing a normal game, to make sure
that was not blocked).

So I am afraid that we have to do an immediate 4.6.2 release to correct this.

:-(

[Arun Persaud]

Hi

On 04/17/2012 03:28 AM, h.g. muller wrote:

> I am very sorry, but it seems I made a major foul-up this time.
>
> One of the latest patches I made breaks XBoard very badly for playing
> engine-engine games in a variant. The test I added to check if the second
> engine supports the variant is made before that engine is actually started
> (and has told XBoard what variants it plays). So the test always fails,
> and XBoard refuses to switch to two-machines mode.
>   There is a work-around, which is to make sure the second engine has
> already been started, e.g. by opening Engine #2 Settings, or playing a game
> in variant normal, before using TwoMachines mode. But this is not possible
> in engine matches or tournaments. I must have done one of these things
> when testing the feature (probably first playing a normal game, to make
> sure
> that was not blocked).
>
> So I am afraid that we have to do an immediate 4.6.2 release to correct
> this.

I can do this tonight. Perhaps we should post this as known bug on the
4.6.1 page?

HGM: When you create the 4.6.2 page, can you also update the front page
to point to the new releases?

Arun

[h.g.muller]

> I can do this tonight. Perhaps we should post this as known bug on the
> 4.6.1 page?

I would be in favor of putting 4.6.1 and 4.6.2 on the same page (a 4.6.2
page, really), starting with the message that 4.6.1 was severely broken
due to a faulty bugfix, and is superseded by 4.6.2. And then simply keep
the list we have there now, adding the minor thing about the castling
rights.

> HGM: When you create the 4.6.2 page, can you also update the front page
> to point to the new releases?

OK, will do.
H.G.