You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stefan Bodewig <bo...@apache.org> on 2011/07/22 06:18:24 UTC
[compress] Proposed Roadmap
Hi all,
>From the responses in the Java5 thread I propose the following.
(1) Release current trunk minus a few lines of code I already added for
initial Zip64 support plus some minor changes ASAP as 1.2
(2) Require Java5, use minimal Java5 language features to make compiler
warnings go away, Zip64 and Pack200, maybe some other JIRAs,
release 1.3
(3) Completely embrace Java5, use generics and enums, switch package
name to compress2 and tackle the backwards incompatible changes we'd
like to take.
This is not a vote, yet, but if there seems to be consensus I volunteer
to be the release manager of the next release and drive the process with
a more concrete proposal for the 1.2 release.
Sure, I've never done any release in Commons before (or performed any
release with mvn at all) so this may slow down the whole process by a
few days and make me ask embarassing questions, but I think we can live
with that.
As far as timeline goes, I see the 1.2 release really soon as in "next
week" while 1.3 probably is a few weeks of coding away. Right now my
available time comes in bursts and I have a pretty clear picture of how
to implement Zip64 but cannot reliably estimate when it will be ready.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Proposed Roadmap
Posted by Christian Grobmeier <gr...@gmail.com>.
Snappy looks pretty cool!
I created an issue for it:
https://issues.apache.org/jira/browse/COMPRESS-147
Without a fix version ;-)
Cheers
On Sat, Jul 23, 2011 at 1:49 PM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2011-07-23, Simone Tripodi wrote:
>
>> I think it would be nice having also s pure Java implementation of the
>> Snappy[1] compression (the Google's compression),
>
> Absolutely, it is just a matter of getting it coded 8-)
>
>> I found a Java implementation[2] but it's JNI wrapper :/
>
> Well, that could be a start.
>
>> Unfortunately my C++ skills are horrible but I'm available to help :P
>
> Any help is welcome.
>
> Cheers
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Proposed Roadmap
Posted by Stefan Bodewig <bo...@apache.org>.
On 2011-07-23, Simone Tripodi wrote:
> I think it would be nice having also s pure Java implementation of the
> Snappy[1] compression (the Google's compression),
Absolutely, it is just a matter of getting it coded 8-)
> I found a Java implementation[2] but it's JNI wrapper :/
Well, that could be a start.
> Unfortunately my C++ skills are horrible but I'm available to help :P
Any help is welcome.
Cheers
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Proposed Roadmap
Posted by Simone Tripodi <si...@apache.org>.
Hallo Stefan!!!
I think it would be nice having also s pure Java implementation of the
Snappy[1] compression (the Google's compression), I found a Java
implementation[2] but it's JNI wrapper :/
WDYT? Unfortunately my C++ skills are horrible but I'm available to help :P
Alles gute!, all the best,
Simo
[1] http://code.google.com/p/snappy/
[2] http://code.google.com/p/snappy-java/
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Sat, Jul 23, 2011 at 5:45 AM, Stefan Bodewig <bo...@apache.org> wrote:
> Hi,
>
> I've moved some JIRA issues that are clear they'll need to break the API
> to 2.0 and assigned a few JIRAs where a patch is available or I would
> know how to implement them to 1.2 and 1.3.
>
> Please review
> <https://issues.apache.org/jira/browse/COMPRESS#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel>
>
> There are some open issues that could be assigned as well like for
> example COMPRESS-111 which mainly requires a way to make use of an
> external library that is not available in any Maven repo.
>
> 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
Re: [compress] Proposed Roadmap
Posted by Stefan Bodewig <bo...@apache.org>.
Hi,
I've moved some JIRA issues that are clear they'll need to break the API
to 2.0 and assigned a few JIRAs where a patch is available or I would
know how to implement them to 1.2 and 1.3.
Please review
<https://issues.apache.org/jira/browse/COMPRESS#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel>
There are some open issues that could be assigned as well like for
example COMPRESS-111 which mainly requires a way to make use of an
external library that is not available in any Maven repo.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Proposed Roadmap
Posted by sebb <se...@gmail.com>.
On 22 July 2011 05:18, Stefan Bodewig <bo...@apache.org> wrote:
> Hi all,
>
> From the responses in the Java5 thread I propose the following.
>
> (1) Release current trunk minus a few lines of code I already added for
> initial Zip64 support plus some minor changes ASAP as 1.2
>
> (2) Require Java5, use minimal Java5 language features to make compiler
> warnings go away, Zip64 and Pack200, maybe some other JIRAs,
> release 1.3
>
> (3) Completely embrace Java5, use generics and enums, switch package
> name to compress2 and tackle the backwards incompatible changes we'd
> like to take.
>
> This is not a vote, yet, but if there seems to be consensus I volunteer
> to be the release manager of the next release and drive the process with
> a more concrete proposal for the 1.2 release.
Sounds good in general.
However, I'm not sure one can prevent the compiler warnings without
either adding generics or adding @SuppressWarnings to the classes
(which will later need to be removed, so any such additions should be
flagged as temporary). We shall see.
> Sure, I've never done any release in Commons before (or performed any
> release with mvn at all) so this may slow down the whole process by a
> few days and make me ask embarassing questions, but I think we can live
> with that.
>
> As far as timeline goes, I see the 1.2 release really soon as in "next
> week" while 1.3 probably is a few weeks of coding away. Right now my
> available time comes in bursts and I have a pretty clear picture of how
> to implement Zip64 but cannot reliably estimate when it will be ready.
>
> 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
Re: [compress] Proposed Roadmap
Posted by Christian Grobmeier <gr...@gmail.com>.
sounds good :-)
On Fri, Jul 22, 2011 at 6:18 AM, Stefan Bodewig <bo...@apache.org> wrote:
> Hi all,
>
> From the responses in the Java5 thread I propose the following.
>
> (1) Release current trunk minus a few lines of code I already added for
> initial Zip64 support plus some minor changes ASAP as 1.2
>
> (2) Require Java5, use minimal Java5 language features to make compiler
> warnings go away, Zip64 and Pack200, maybe some other JIRAs,
> release 1.3
>
> (3) Completely embrace Java5, use generics and enums, switch package
> name to compress2 and tackle the backwards incompatible changes we'd
> like to take.
>
> This is not a vote, yet, but if there seems to be consensus I volunteer
> to be the release manager of the next release and drive the process with
> a more concrete proposal for the 1.2 release.
>
> Sure, I've never done any release in Commons before (or performed any
> release with mvn at all) so this may slow down the whole process by a
> few days and make me ask embarassing questions, but I think we can live
> with that.
>
> As far as timeline goes, I see the 1.2 release really soon as in "next
> week" while 1.3 probably is a few weeks of coding away. Right now my
> available time comes in bursts and I have a pretty clear picture of how
> to implement Zip64 but cannot reliably estimate when it will be ready.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Proposed Roadmap
Posted by Gary Gregory <ga...@gmail.com>.
This all sounds good to me.
Gary
On Jul 22, 2011, at 0:19, Stefan Bodewig <bo...@apache.org> wrote:
> Hi all,
>
> From the responses in the Java5 thread I propose the following.
>
> (1) Release current trunk minus a few lines of code I already added for
> initial Zip64 support plus some minor changes ASAP as 1.2
>
> (2) Require Java5, use minimal Java5 language features to make compiler
> warnings go away, Zip64 and Pack200, maybe some other JIRAs,
> release 1.3
>
> (3) Completely embrace Java5, use generics and enums, switch package
> name to compress2 and tackle the backwards incompatible changes we'd
> like to take.
>
> This is not a vote, yet, but if there seems to be consensus I volunteer
> to be the release manager of the next release and drive the process with
> a more concrete proposal for the 1.2 release.
>
> Sure, I've never done any release in Commons before (or performed any
> release with mvn at all) so this may slow down the whole process by a
> few days and make me ask embarassing questions, but I think we can live
> with that.
>
> As far as timeline goes, I see the 1.2 release really soon as in "next
> week" while 1.3 probably is a few weeks of coding away. Right now my
> available time comes in bursts and I have a pretty clear picture of how
> to implement Zip64 but cannot reliably estimate when it will be ready.
>
> 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