Remaining issues for 3.2.0-beta4

Development
1

I was hoping to try releasing 3.2.0 by 1 October, but that’s obviously not happened. There’s one more change I’d like to get wider testing before we release 3.2.0. Bugs 2711 and 4452, which are among the top 15 most reported open bugs, as well as a few others, can be corrected by upgrading from Batik 1.7 to a pre-release version of Batik 1.8. I haven’t been able to get Batik 1.8pre to work properly yet, and have posted to the Batik list about it, so hopefully I’ll soon have a solution.

I’ll pick up any bug fixes that are outstanding at the time I get the fix for the Batik upgrade, and then I’d like to release 3.2.0-beta4, and then 3.2.0 maybe two weeks after that.

2

I found the solution to the problem with Batik 1.8pre today with the help of the Batik mailing list, so Bugs 2711, 2746, 3745, and 4452 are all fixed now.

I’ll release 3.2.0-svn8412 as 3.2.0-beta4 tomorrow, if there are no objections.

vassalengine.org/~uckelman/builds/

3

What’s the latest? (on Oct-12-12)

VASSAL-3.2.0-svn8417
or
VASSAL-3.2.0-beta4

Thanks

4

Thus spake Flaney:

What’s the latest? (on Oct-12-12)

VASSAL-3.2.0-svn8417
or
VASSAL-3.2.0-beta4

3.2.0-beta4.

–
J.

5

Is 3.2betabuild8426 still beta 4? I see the last update was on 10-30.

6

Thus spake mille1212:

Is 3.2betabuild8264 still beta 4? I see the last update was on 10-30.

beta4 was svn8419. The current dev build is svn8426.

–
J.