Thanks Tim! Replies in line.
- Bob
On 9/19/2016 12:33 PM, Allison, Timothy B. wrote:
Bob,
As always, thank you for driving 2.0!
My concern is we have been dual maintaining 2 branches for about 9 months. I
think the longer we do this the more risk there is that we miss something.
Agreed. I think we're already missing a few things.
Yikes is there a way we can audit what we might have missed? Perhaps we
need a JIRA to do an audit of the commits in master and do a best effort
of what might have been missed? I can create the JIRA for this.
Would it make sense to at least put a date out there for a feature cut off?
I'd be hesitant to do this. To my mind, the key is the actual features and
devs who have time to implement them.
Ok this is a start to understand what the blocking features are. The key
will be creating concrete JIRAs for them and identifying where we are at.
For me, the blocking new features are:
1) Implement various strategies for chaining multiple parsers against
individual files. Much of this has been implemented, but what's holding us up
on this one (I think?) is a resettable outputstream.
I think we need a JIRA for this. Is there any existing design ideas on
how this would be achieved?
2) Rich metadata (TIKA-1607)
This is great. I think we need to ensure we have JIRAs for all the
features we consider blockers and label them as such. This looks like
there's a lot of good discussion. It also references TIKA-1903 so is
that also a Tika 2.0 blocker?
The blocking tasks:
1) Get rid of old metadata tags in favor of "new" Dublin core
Need JIRA?
2) ???
If we can't get a date we should at least try to eliminate the ???. I
think we need to close down the feature set.
I'm full up on other stuff at the moment, perhaps after we get 1.14 out, I can
turn to 2.0-specific development.
What else do we have to do? Anyone else have some time?
Yes please would be great to see if there are people that want to own
work on the above features. Once we have JIRAs we can post to the
Apache Help Wanted page as well.
Thanks!
Cheers,
Tim
-----Original Message-----
From: Bob Paulin [mailto:b...@bobpaulin.com]
Sent: Monday, September 19, 2016 10:32 AM
To: dev@tika.apache.org
Subject: Re: Plans for the first Tika 2.0 release
Hi,
I think it's a good thing to discuss. I know there are other features that are
targeted for 2.0. Do we have a general sense of where those features are at?
My concern is we have been dual maintaining 2 branches for about 9 months. I
think the longer we do this the more risk there is that we miss something.
Would it make sense to at least put a date
out there for a feature cut off? There's always 3.0 if things are not
close to being ready.
- Bob
