Hi Keith: > > This is pretty urgent for me -- I have a software deadline tonight and I'd > like to use a version of Tika that is checked into subversion. If it's ok > with you I'd like to commit the TIKA-81 patch this afternoon, and we can > devise a longer term solution later. >
For a small piece of agreed upon functionality this is fine, but I just want to clarify that commits/patches/etc. should not necessarily be driven by the deadlines of a single developer. Again, in this case it's fine: this was a small piece of code that was universally agreed upon and added functionality: rather than reorganized, or removed it. In the future though, I think it should be discouraged to allow such timelines to be a driver for committing patches. In this case, you waited 7 minutes (as far as I can tell) between sending your last email and committing the patch. Seeing as though we all live in different locations/timezones, etc., this wasn't even enough time for (m)any folks to reply. I just wanted to send this as a heads up to you as far as my preference. The other developers may have their own, which they are entitled to. Cheers, Chris ______________________________________________ Chris Mattmann, Ph.D. [EMAIL PROTECTED] Cognizant Development Engineer Early Detection Research Network Project _________________________________________________ Jet Propulsion Laboratory Pasadena, CA Office: 171-266B Mailstop: 171-246 _______________________________________________________ Disclaimer: The opinions presented within are my own and do not reflect those of either NASA, JPL, or the California Institute of Technology.
