Ahh, gotcha. Just ship the updated CHANGES to [2] and then maybe update in trunk, right? That's fine by me. I'll also update the sig file name to match the tika src zip per Nick's suggestion and call it done until the VOTE passes.
Will do. Cheers, Chris On Sep 26, 2011, at 8:49 AM, Jukka Zitting wrote: > Hi, > > On Mon, Sep 26, 2011 at 5:44 PM, Mattmann, Chris A (388J) > <chris.a.mattm...@jpl.nasa.gov> wrote: >> If that's the case, I'd prefer to simply update CHANGES.txt in the RC zip >> file, >> in the tag and the branch I'll create (and trunk), and then update the .asc >> file. > > I'd just update the file at [1] (that I guess will go to [2] if the > vote passes), but leave svn and the signed zip file untouched. If you > change the tag or the source zip, it's best to re-cut the entire RC > since we'll in any case need to verify the new signatures, etc. > > [1] http://people.apache.org/~mattmann/apache-tika-0.10/rc1/CHANGES-0.10.txt > [2] http://www.apache.org/dist/tika/CHANGES-0.9.txt > > BR, > > Jukka Zitting ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
