Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 209.85.220.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <87d3e3d2ys.fsf@v35516.1blu.de>
References: <87d3e3d2ys.fsf@v35516.1blu.de>
Date: Tue, 11 Oct 2011 15:27:15 +0100
Message-ID: 
 <CAOGo0VYi5gcjGXBVAOZ8-SnpdQ9TPhUOneCPHQTYWX7wZP90Vg@mail.gmail.com>
Subject: Re: [compress] Planning for a 1.3 Release?
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 11 October 2011 15:20, Stefan Bodewig <bodewig@apache.org> wrote:
> Hi all,
>
> its been quite some time since I finished the Zip64 stuff and I think we
> are at the point we discussed three month ago or so: release Compress
> 1.3 even if it doesn't have many big changes when compared to 1.2. =A0In
> addition to Zip64 we have read-only support for Unix dump and also
> Pack200 "compression". =A0Documentation is fairly complete IMHO.
>
> One thing that we may or may not want to address are the integration
> tests for Zip64 which are currently only run when the run-it profile is
> enabled. =A0These tests need some zips generated by other tools that are
> currently not part of svn and we discussed publishing them as separate
> artifacts - personally I wouldn't even know where to start for this.

So long as it is clear to users how to set up in order to run the
tests, I think the tests can remain as they are.

> Then we do have some JIRAs with patches in particular one for XZ
> compression and patches for compressors where a single container stream
> contains multiple compressed streams (I didn't know gzip and bzip2 could
> do that, I must admit), all by Lasse Collin.
>
> The XZ patch has the "problem" that it introduces a new dependency - do
> we want that or would we prefer a separate module? =A0In addition XZ for
> Java is not available via any Maven repo, yet, this may require some
> tweaking during build time (Ant <get> task?). =A0Shall we defer this unti=
l
> after the 1.3 release?

+1

> The other two patches should be addressed together with changing the API
> in 2.0, IMHO.

+1

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

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