The short answer is that we’re getting closer now, but the process is organic.
The long answer is that with regard to the APIs which I work on, we need the newer features to become stable before doing a release candidate. This is just a case of waiting a few weeks for new APIs to be used by people and for bugs to be opened against them on JIRA. This often results in breaking API changes being necessary to fix assumptions or design flaws. Right now this applies to, parsing, font embedding and forms. Milestones for the trunk aren’t particularly helpful as we don’t and can’t offer any kind of stability and you’re always better off using the latest trunk - there are snapshot builds available already. We’ve reached the point with 2.0 where most of the remaining issues and bugs probably fall into the “pdf expert” category. On the plus side we’re now down to under 70 open issues. -- John > On 2 Feb 2015, at 05:07, Jan De Moerloose <[email protected]> > wrote: > > Hi, > > as i did not get an answer, i assume there is no planning yet ? Would it be > possible to tag a version as release candidate or milestone instead ? > I would be willing to dedicate a small amount of time if that helps, but the > list of open issues for this version is daunting (100+). Please let me know > if there is anything i can help with (as a java programmer, not a pdf > specialist). > Btw, the product works fine for me, so thanks to all developers for doing > such a great job !!! > > cheers, > Jan > On 01/12/2015 02:07 PM, Jan De Moerloose wrote: >> Hi, >> >> i am using a snapshot version of pdfbox 2.0.0 for converting pdf's to >> images. Is there already a time schedule for the release of this version ? >> >> Regards, >> Jan >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
