I'm very interested to know what the general level of enthusiasm for a formal release sometime soon might be?
My specific driver is to see Maven Central serve a version of FOP which fixes https://issues.apache.org/bugzilla/show_bug.cgi?id=54094 [break-before="page" causes IllegalArgumentException] In that bug report, Luis Bernardo indicated it was fixed what is now 18 months ago (in trunk in July 2012 but after the RC for 1.1 was put forward). I appreciate I could repackage FOP into a package namespace I control, and put that into Maven Central, but obviously that's best avoided if possible... So I'm wondering what are the major areas if any which need to stabliise before a release would likely pass a vote? thanks .. Jason On Wed, Aug 28, 2013 at 6:11 PM, Vincent Hennebert <[email protected]> wrote: > > Time to sum up. We have 6 +1, the vote passes. > > That said, there have been reservations expressed about the dependency > on a patched version of Batik. So I’ll defer the merge until the PMC has > found a viable solution for Batik’s future. > > Thanks, > Vincent > > On 21/08/13 12:08, Vincent Hennebert wrote: > > This work allows to directly use FOP-configured fonts for SVG images, > > instead of trying to find, via AWT, equivalent fonts installed on the > > system, and then mapping them to FOP fonts when generating the output. > > > > Please note that this introduces a dependency on the trunk version of > > Batik, with the patch from BATIK-1041 applied. That means that before > > releasing the next version of FOP, a new version of Batik will have to > > be released first. > > > > This vote will run until Monday, 26 August 11:00 UTC. > > > > +1 from me. > > > > Thanks, > > Vincent > >
