lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Ernst (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6258) Cut binary releases down to a single format
Date Thu, 19 Feb 2015 18:22:12 GMT


Ryan Ernst commented on LUCENE-6258:

a) worth looking at the build.xml files to make sure we understand what is currently diff
between the two – off the top of my head i seem to recall line endings on shell scripts
being diff (to play nicer with cygwin when windows users use zip files) ... on the flip side:
tgz lets us preserve executable bits on shell scripts in a way i don't believe works consistently
in zip files? ... point is: that should be reviewed thoroughly before ripping out one or the

If this is true, that we have different line endings depending on the format, then this is
bogus IMO. We don't say "windows" and "unix/mac" in the filename to indicate zip is for one
and tgz for the others.

b) this sounds like a made up problem to me -- end users are only helped by having multiple
formats, not harmed.  users aren't downloading both the tgz and zip file releases -- they
are picking one and using that.  the only size decrease here is in what we as developers have
to download to test when voting on an RC.

But that is a real problem. Releases take a *long time* for the release manager to deal with.
 Cutting down on what has to be transferred/tested will allow us iterate more quickly. For
example, maybe we wouldn't be so afraid of a respin if spinning an RC took half the time (not
saying this will decrease the time by half, only using this as an example for why decreasing
total artifacts size is good for us).  

Regarding "end users are only helped", then why don't we also release in .7zip, or .rar or
any other container format?  Why is our source release only for tgz? IMO it is because we
just need some container format to stuff our jar files into. There is no real distinction
or advantage for a competent user.

> Cut binary releases down to a single format
> -------------------------------------------
>                 Key: LUCENE-6258
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Ryan Ernst
> In LUCENE-6247, one idea discussed to decrease the size of release artifacts was removing
either tgz or zip from our binary releases.
> The source releases are already only in tgz.  I think we should do the same for binary
releases.  I looked at a number of other Apache projects, and the results are mixed, but there
definitely are many major projects (hadoop, couchdb, cassandra, cordova) that only release
tgz. Anyone who can deal with running using Lucene or Solr should have the skills necessary
to extract an archive in either format, so in this way I think either format is fine, but
I think matching what we release source in has a nice look.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message