Hi, On Dec 21, 2007 6:20 PM, Chris Mattmann <[EMAIL PROTECTED]> wrote: > No update on the release because I never heard back from a consensus on > whether or not I should go forward with it? :)
Ah, sorry. +1 from me. :-) > I've got plenty of spare cycles over the next few weeks myself, as I'm on > winter break, so I'm very happy to make the release. Should I start on it > now, or do we need to call a vote for it first? OK, cool. No need to call a vote, I think we have good consensus that it's time to make the 0.1 release. > We also never really came to agreement on how the release should be made? > I'm +1 for releasing a src *.tar.gz and a bin *.tar.gz (that has the tika > jar in it, w/o dependencies) as an aggregated single *.tar.gz, with the > LICENSE.txt, CHANGES.txt, README.txt and NOTICE.txt files included. Is > everyone else OK with it? Does everyone else need to be OK? :), or can I > simply move on as the release manager on this without getting a consensus? Basically you're free to produce any kind of a release candidate, but it won't become an official release before we (and the Incubator PMC) votes to approve it for release. And to get the approval the release needs to comply with the ASF policies on releases. See http://incubator.apache.org/guides/releasemanagement.html for all the details. Our main release artifact needs to be the source code, and if we want we can also include binary artifacts built from the released source. Our svn structure is quite good, so I'd simply use a packaged svn export as the source release. Something like this: svn export \ http://svn.apache.ort/repos/asf/incubator/tika/tags/0.1-incubator \ apache-tika-0.1-incubator jar cMf apache-tika-0.1-incubator-src.jar apache-tika-0.1-incubator or tar zcf apache-tika-0.1-incubator-src.tar.gz apache-tika-0.1-incubator Using jar to package the sources makes things easier for people (Windows users) who don't have tar readily available. Like Sami, I think having a binary tarball isn't that essential. Instead we should make the binary jar artifact available in a Maven repository. To prepare such a release candidate, I'd use: cd apache-tika-0.1-incubator mvn deploy -DaltDeploymentRepository=stage::default::file:///path/to/tika/staging/repository You can make that staging repository available as the binary part of the release candidate. After the vote we can simply copy the approved artifacts over to a real Maven repository without having to rebuild them. BR, Jukka Zitting
