Mailing-List: contact general-help@xmlgraphics.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@xmlgraphics.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <BLU436-SMTP166C9928D760A786169EEE2FBFF0@phx.gbl>
References: <DUB120-W248BA988C7FB6A6CFAB671863C0@phx.gbl>
 <CABKGwxndrE7rOiXHuxfdbE7_AbiUZzLk=q3vB-ECHAcYQ3Uwug@mail.gmail.com>
 <079BBD1C-57D8-43D2-9001-1F78E1FD80AC@gmail.com>
 <DUB120-W35812CBB61A522E698A1FA86250@phx.gbl>
 <CABKGwxmP1oSe1eBRiWTB-uH7Y9pn-VS8+vGxLJ4Ww4XZQ9OLyA@mail.gmail.com>
 <DUB120-W2659CD465ACC7BEDB6A6F186270@phx.gbl>
 <029201cf7c0d$cf1395a0$6d3ac0e0$@gmail.com>
 <DUB120-W23E5FAE0B8128320C66E1E86270@phx.gbl>
 <06425F34-8B02-4145-B24E-0C02A1D324E2@gmail.com>
 <BLU436-SMTP577286695C1EEEDCD606A0FB200@phx.gbl>
 <DUB120-W4218256A2193C9CFCF6F6A86F60@phx.gbl>
 <CACQ=j+eWe=_9FhCGnwk-mrDPfdujN1hU_AsHWoHimtKgzU-mag@mail.gmail.com>
 <FF97C3F6-851D-47D6-80D9-CBD97C01818E@gmail.com>
 <CACQ=j+fMNJF=a3z6PrO+qev=POvYrCctZ6sWcQZG76aynrzG6A@mail.gmail.com>
 <3B1130B4-B339-4382-98D2-2549AECBF3D6@gmail.com> <53C6684B.2080302@gmail.com>
 <012101cfa10c$91820310$b4860930$@gmail.com> <53C6B52D.1010407@gmail.com>
 <CACQ=j+drZ4m1-MM3w2th0g95ruhwE+hq_0Hcz-sEUSZ9F8r76Q@mail.gmail.com>
 <BLU436-SMTP166C9928D760A786169EEE2FBFF0@phx.gbl>
From: Glenn Adams <glenn@skynav.com>
Date: Thu, 24 Jul 2014 07:41:28 -0600
Message-ID: 
 <CACQ=j+doCOvJNhH6GdDzt+Py+Hg7t=TbB2NJmVp9dtChbpfYeA@mail.gmail.com>
Subject: Re: New FOP Release [was: Re: FOP Release Automation]
To: XML Graphics Project <general@xmlgraphics.apache.org>
Content-Type: multipart/alternative; boundary=047d7bfcfc0650f3d404fef09e6b

--047d7bfcfc0650f3d404fef09e6b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 24, 2014 at 6:39 AM, Chris Bowditch <bowditch_chris@hotmail.com=
>
wrote:

> Hi Glenn,
>
> The original plan was for Robert Meyer to handle the release. I've moved
> him to a different project for a while, so I then decided Vincent should =
be
> our volunteer ;-)
>
> However, it came to light that there is an unwritten policy that releases
> can't depend on snapshots of other projects. So that's causing us a probl=
em
> for the pdf-plugin and font merging enhancement, which is one of several
> key features in this release. The PMC needs to decide if a snapshot
> dependency is acceptable or whether we should wait for PDFBox v2.0 to be
> released.
>

Is there a schedule (tentative or otherwise) for releasing PDFBox 2.0?


>
> Vincent is currently looking additional bugs to fix before the release.
> Can we continue this discussion on general@ please, since this affects
> all projects, not just FOP
>

Sure.


>
> Thanks,
>
> Chris
>
> On 16/07/2014 18:33, Glenn Adams wrote:
>
>>
>>
>>
>> On Wed, Jul 16, 2014 at 11:23 AM, Vincent Hennebert <vhennebert@gmail.co=
m
>> <mailto:vhennebert@gmail.com>> wrote:
>>
>>     On 16/07/14 17:42, Simon Steiner wrote:
>>
>>         Hi,
>>
>>         I switched fop back to fontbox 1.8, so its only the pdfplugin
>>         that uses 2.0 and the user would delete 1.8 jar if copying
>>         pdfplugin to fop.
>>
>>
>>     Thanks Simon. That=E2=80=99s great because that means that we can st=
art the
>>     release process of FOP as soon as we are ready.
>>
>>
>> It would be nice to share the following info:
>>
>>   * who is going to take the lead on performing the release?
>>   * what is a tentative schedule for release, e.g., when should last
>>     changes be integrated?
>>   * what additional integrations (if known) are planned before release?
>>
>>
>>
>>
>>     Vincent
>>
>>
>>         Thanks
>>
>>         -----Original Message-----
>>         From: Vincent Hennebert [mailto:vhennebert@gmail.com
>>         <mailto:vhennebert@gmail.com>]
>>         Sent: 16 July 2014 12:56
>>         To: fop-dev@xmlgraphics.apache.org
>>         <mailto:fop-dev@xmlgraphics.apache.org>
>>         Subject: New FOP Release [was: Re: FOP Release Automation]
>>
>>         Hi,
>>
>>         On 15/07/14 16:53, Clay Leeds wrote:
>>
>>             On Jul 15, 2014, at 7:46 AM, Glenn Adams <glenn@skynav.com
>>             <mailto:glenn@skynav.com>> wrote:
>>
>>                 I suppose it depends on whether or not we need to hack
>>                 perl to use the facility. If there is any alternative
>>                 that doesn't use perl, then that would be preferable.
>>
>>                 Frankly, I've never been happy with the new MD based
>>                 documentation, though Clay has spent an inordinate
>>                 amount of time tweaking it.
>>
>>
>>             Yeah... It's not my favorite either, but at least edits
>>             are pretty quick, saved to SVN and we've got a solution to
>>             incorporate javadoc, etc.
>>
>>             In the meantime, please let me know when we're ready to
>>             update the
>>             documentation for the Release. It doesn't take me very
>>             long to go
>>             through the code to make these types of batch edits.
>>
>>         <snip/>
>>
>>         Clay, your offer to help would be greatly appreciated!
>>
>>         And since you=E2=80=99re mentioning it, maybe it=E2=80=99s time =
to think about
>>         making a new release of FOP. Although now that the font
>>         merging code has been merged to trunk, and introduces a
>>         dependency on FontBox 2.0.0, we would have to wait that
>>         FontBox 2.0.0 is released first. Or adapt the code to keep the
>>         former 1.8.5 dependency (or the newer 1.8.6 released version).
>>
>>         In the meantime, can anybody think of features that should
>>         definitely be implemented before the release, or bugs fixed?
>>         Remember that due to API changes, that release will have to be
>>         called 2.0.
>>
>>         Thanks,
>>         Vincent
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
>

--047d7bfcfc0650f3d404fef09e6b--