lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-6258) Cut binary releases down to a single format
Date Thu, 19 Feb 2015 18:45:14 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327933#comment-14327933
] 

Hoss Man commented on LUCENE-6258:
----------------------------------

bq. 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.

maybe we should? ... my memory may also be faulty.  my point is: before throwing away a file
type, it's worth looking at why we have that file type.

bq. Regarding "end users are only helped", then why don't we also release in .7zip, or .rar
or any other container format?

maybe we should? ... the point here is: i think decisions about what formats we release binary
artifacts should primarily be drive by whats best for the user, not what makes life easier
for developers.

---

bq. 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.

if that's the goal of this issue then the summary & description are somewhat missleading
and confusing. cutting down on the amount of time/work needed for the release manager is a
different question/problem then "let's remove some of the files we release to end users" 

FWIW: there are a lot of things that could be done to simplify the time/energy for the release
manager. i already tried to suggest some back in LUCENE-5589 -- notably  having jenkins automate
as much as possible, and switching to (the more reliable then people.apache.org) dist.apache.org
for hosting the RCs, which would also minimizing the amount of network bandwidth the RC manager
has to use -- my suggestions were dismissed "in toto", w/o any consideration for the basic
premise that the release process might be stream lined & speed up independently of just
trying to hack away and remove bytes from disk.


> Cut binary releases down to a single format
> -------------------------------------------
>
>                 Key: LUCENE-6258
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6258
>             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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message