Tagua PGN load/save support ; short term release plans

[Yann Dirson]

Hi all,

First, let's inaugurate this brand new mailing list! I've CC'd a
couple of people, both contributors and people who showed some
interest about tagua in the recent months, since I don't know who has
already subscribed - sorry if you received this email twice. The
others may want to visit http://groups.google.com/group/tagua-devel -
and/or join #tagua on irc.freenode.net, where discussion can be
easier.

I have done some work recently on the master branch, to get PGN
load/save into a better shape. Those patches make it possible to load
and save games of any variant. The only major problem I noticed and
did not fix yet is the loading of games containing variations.

Those patches are available from http://repo.or.cz/w/tagua/yd.git :

pgn-variants | Fix failed assertion loading PGN for a variant.
shogi-deserialize | Implement for shogi deserialization of the notation used for saving PGN
pgn-save-variant | Record variant name in PGN file, so they can be read accordingly.

Secondly, maybe wecould organize developement a bit, while waiting for
Paolo to be back.

There are still a couple of annoying things in master, but there were
already a number of useful improvements (a couple of translations,
load/save support, new shogi variants, many bugfixes). As the
component-api branch is not yet ready for general use, and since KDE4
has now been released, I thought it could be a good idea to squash a
couple of more annoying bugs and release a second alpha, before merging
the component-api branch onto master and progress towards a beta.

How would you feel about this plan ?

Best regards,
--
Yann.

[Paolo Capriotti]

Hi all,

Yann Dirson wrote:
>
> Those patches are available from http://repo.or.cz/w/tagua/yd.git :
>
> pgn-variants | Fix failed assertion loading PGN for a variant.
> shogi-deserialize | Implement for shogi deserialization of the notation used for saving PGN
> pgn-save-variant | Record variant name in PGN file, so they can be read accordingly.

Good. I've merged the patches.

> There are still a couple of annoying things in master, but there were
> already a number of useful improvements (a couple of translations,
> load/save support, new shogi variants, many bugfixes). As the
> component-api branch is not yet ready for general use, and since KDE4
> has now been released, I thought it could be a good idea to squash a
> couple of more annoying bugs and release a second alpha, before merging
> the component-api branch onto master and progress towards a beta.
>
> How would you feel about this plan ?

As I told you on IRC, I like it a lot. We should be able to focus on the
component API after this second alpha, then merge the branch and release
a beta.

I'll write on our trac (http://trac.tagua-project.org/) what I think
should be the main objectives of the next release, and a tentative
release date.

Paolo