You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by Jukka Zitting <ju...@gmail.com> on 2007/12/21 10:41:29 UTC
Tika 0.1 update
Hi,
Chris, any update on the Tika 0.1 release? I don't think we have any
blockers open, and the six issues currently tagged for 0.1-incubator
could IMHO well be postponed to future releases.
If you like, I could take on managing the release as I'll have some
spare cycles (between pushing for Jackrabbit 1.4 :-) next week.
BR,
Jukka Zitting
Re: Tika 0.1 update
Posted by Bertrand Delacretaz <bd...@apache.org>.
> ...On Dec 21, 2007 6:20 PM, Chris Mattmann <ch...@jpl.nasa.gov> wrote:
> > No update on the release because I never heard back from a consensus on
> > whether or not I should go forward with it? :)...
+1 for going forward.
On Dec 21, 2007 8:50 PM, Jukka Zitting <ju...@gmail.com> wrote:
> ... tar zcf apache-tika-0.1-incubator-src.tar.gz apache-tika-0.1-incubator
Nitpick: according to [1] the artifacts must include "incubating" in
their name, not "incubator".
-Bertrand
[1] http://incubator.apache.org/guides/releasemanagement.html
Re: Tika 0.1 update
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Dec 21, 2007 6:20 PM, Chris Mattmann <ch...@jpl.nasa.gov> 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
Re: Tika 0.1 update
Posted by Sami Siren <ss...@gmail.com>.
Chris Mattmann wrote:
> 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?
>
> My proposal:
>
> Release format: single *.tar.gz
> Release name: tika-0.1.tar.gz
> Contents: ./tika-src-0.1.tar.gz
> ./tika-bin-0.1.tar.gz
> ./LICENSE.txt
> ./NOTICE.txt
> ./CHANGES.txt
> ./README.txt
> Release Manager for 0.1: Chris
> Release Manager for 0.2: Jukka
>
> Is this acceptable? If so, I will start on the release today.
Tar balls are ok with me. More important thing IMO is to get the
released artifacts into some repository.
--
Sami Siren
Re: Tika 0.1 update
Posted by Chris Mattmann <ch...@jpl.nasa.gov>.
Hi Jukka,
No update on the release because I never heard back from a consensus on
whether or not I should go forward with it? :)
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?
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?
My proposal:
Release format: single *.tar.gz
Release name: tika-0.1.tar.gz
Contents: ./tika-src-0.1.tar.gz
./tika-bin-0.1.tar.gz
./LICENSE.txt
./NOTICE.txt
./CHANGES.txt
./README.txt
Release Manager for 0.1: Chris
Release Manager for 0.2: Jukka
Is this acceptable? If so, I will start on the release today.
Thanks!
Cheers,
Chris
On 12/21/07 1:41 AM, "Jukka Zitting" <ju...@gmail.com> wrote:
> Hi,
>
> Chris, any update on the Tika 0.1 release? I don't think we have any
> blockers open, and the six issues currently tagged for 0.1-incubator
> could IMHO well be postponed to future releases.
>
> If you like, I could take on managing the release as I'll have some
> spare cycles (between pushing for Jackrabbit 1.4 :-) next week.
>
> BR,
>
> Jukka Zitting
______________________________________________
Chris Mattmann, Ph.D.
Chris.Mattmann@jpl.nasa.gov
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.