Hi,

Am 14.10.2014 um 08:16 schrieb John Hewson:
Andreas,

Hi,

Am 10.10.2014 um 20:10 schrieb John Hewson:
Andreas - can we create a new “Later” version in JIRA so that we can assign
issues that we’ve decided to defer until after 2.0? That way we can have a
definitive list of what does and doesn’t need attention.
What exaclty would be the difference between "Later" and "Unscheduled”?

The use of a blank Fix Version to mean “unscheduled” is problematic as there’s
no way to tell a deliberately deferred issue from once which we forgot to 
schedule,
or from the hundreds of historic 1.8 and older issues we have, or from 
version-less
issues such as those related to the web site, so I was thinking that an 
explicit “Later
version would let us proactively and unambiguously defer issues.

Thinking about it, “2.1” and “3.0” labels might be better, for breaking and 
non-breaking
changes, respectively. This way we’re using JIRA for release management as well 
as
bug tracking.
Sounde more reasonable than the "Later" idea. I've added both versions

BR
Andreas Lehmkühler

-- John

BR
Andreas Lehmkühler


-- John


On 10 Oct 2014, at 11:05, John Hewson <j...@jahewson.com> wrote:

Simon,

Andreas has the best handle on this, but off the top of my head what we need is 
to finish
making breaking API changes and for the code to have been stable for a while 
before
making a 2.0 release.

Improvements and fixes which still need breaking API changes include:
        - Pattern rendering
        - Pages resource caching (significant memory usage issues)
        - Font embedding (particularly TTF)
        - Parsing (Andreas?)
        - Page Tree (needs completely re-writing)
        - Text extraction on Java 8 (this might end up being a breaking change 
to the sort)

There’s probably more, such as work on Acroforms, and we need to have much 
better
example code for 2.0 due to all the changes.

This seems like a good time to explicitly try to make sure that we have JIRA 
issues open
for all outstanding tasks, so that we can track how close 2.0 is to being 
ready. The stability
of the code is a pretty good indicator - we’re not there yet.

I’m going to open some JIRA issues. Andreas, Tilman - please open issues for any
2.0 features which you think we need.

Thanks

-- John

On 10 Oct 2014, at 08:08, Simon Steiner <simonsteiner1...@gmail.com> wrote:

Hi,



Could you set a target date for 2.0 release. What's missing to make a
release?



Thanks







Reply via email to