All - I would like to propose as another criterion for releasing 0.1 that the features we expose in the API work correctly (or are documented to not work correctly), and are verified by unit tests. I can volunteer to do some of this, but I am not familiar with some of the features, so I may need to consult with the authors of those features.
Bertrand, thanks for committing TIKA-52. I marked TIKA-56 critical because until it is fixed, Tika will fail to parse documents, and do so in a way that would (reasonably IMO) confuse and surprise a user. I apologize if 'critical' was excessive; major didn't seem urgent enough. If we provide 'detect MIME type functionality by extension' functionality, then even though I am (we are?) a fan of lower case extensions, a large number of users will complain that Tika is broken when it fails to parse files with upper case extensions. Although from a purist's point of view Tika may not be broken, from a pragmatic point of view I think we should consider it so. In my opinion, this should be fixed before 0.1 is released. I believe the fix is trivial in any case. I'd also suggest that another criterion be that the convenience methods in ParseUtils work as expected, and that performing common tasks is reasonably straightforward. I'm not saying that there's a problem, just that as the architecture is changing, we want to make sure that we are not losing or breaking any conveniences, or failing to provide simplifications of common tasks that are trivial to simplify. BTW, Jukka, I'm willing to help with forum moderation too. Regards, Keith Bertrand Delacretaz wrote: > > On 10/12/07, Chris Mattmann <[EMAIL PROTECTED]> wrote: > >> ... Right now looking in JIRA ( >> https://issues.apache.org/jira/browse/TIKA ) we >> have 1 critical and 4 major issues pending. What should the plan be for >> these with respect to the 0.1 release?... > > I just applied the TIKA-52 patch, and I don't think TIKA-56 really > deserves to be marked "critical". > > I'd be fine with a 0.1 release as is, or maybe including TIKA-53 if it > can be finished soon (I'm not planning on working on it right now but > maybe others are?). > > Jukka, I'd be willing to help with forum moderation too. > > >> ...Can we also come up with a >> release schedule... > > At this stage I'd go the other way round: decide which issues we want > to be in 0.1, and release when those are done. In the meantime, avoid > committing disruptive changes to the codebase. > > -Bertrand > > -- View this message in context: http://www.nabble.com/0.1-release--tf4611474.html#a13177764 Sent from the Apache Tika - Development mailing list archive at Nabble.com.
