Hey Nick, On Jul 1, 2012, at 2:52 PM, Nick Burch wrote:
> On Sun, 1 Jul 2012, Mattmann, Chris A (388J) wrote: >> I also plan to spin a 1.2 release candidate at some point in the next week >> or so. I realize the metadata stuff isn't done yet, but it's better to >> simply release early and often, and then when stuff is ready it can be >> included. Releasing is a light-weight process in Tika, so it's no biggie. > > A release does have one big effect though - it firms up the API and requires > us to be backwards compatible with that going forward. What API changes do you envision as part of the metadata stuff? So far, I've seen met key updates, property class stuff, and a new proposed module (tika-xmp) which is great and which I need to review btw :) As for back compat, that's definitely high on the priority list, but so is releasing and we need to be mindful not to let ongoing changes freeze our ability to simply release the software. > It can be a big pain if an in-progress API is suddenly effectively frozen by > the need to be compatible into the future... Agreed -- so, what do you think? How much longer do we need to wrap up the API changes or whatever going on with the metadata stuff? A week? 2 weeks? There's nothing super pressing for me to do an RC, I just brought this up a month ago [1] and received a similar answer, so I'd like us to be able to make a release soon. It would be great to roll a 1.2 RC #1 sometime in the next 2 weeks. Thoughts? Cheers, Chris [1] http://s.apache.org/MFq ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
