On Sun, Jun 29, 2014 at 3:50 PM, Benedikt Ritter wrote:
>
> Alpha, beta, or GA makes no difference if it's made public through maven
> central. As soon as something is available there, people will start to use
> it. This will lead to jar hell, when we decide/have to break BC between
> alpha/beta a
I'm definitely in favor of going for a 1.0 release. I think that the
delay in releasing it introduces more potential problems than the two
open Jira issues that are blocking the release ever will.
- Gabriel
On Tue, Jun 17, 2014 at 4:05 AM, Gary Gregory wrote:
> The public API is OK, and the inte
ency will be the winner in maven. Anyhow, this was the potential
"breakage" that I was inquiring about, but I take it that this isn't
something to worry about here.
- Gabriel
>
> 2014-05-03 10:22 GMT+02:00 Gabriel Reid :
>
>> From what I've seen of the discussion on
aying we should release 1.0 from the current trunk? I
>> would
>> volunteer to RM.
>>
>>
>> 2014-05-02 16:02 GMT+02:00 Gary Gregory :
>>
>>> +1 to keep the discussion going with or without patches. We need to get a
>>> 1.0 out the door.
>
Hi Benedikt,
Thanks for the feedback. My comments are inlined below.
On Fri, May 2, 2014 at 9:41 AM, Benedikt Ritter wrote:
> 2014-05-02 8:15 GMT+02:00 Gabriel Reid :
>> If there are open issues that are specifically standing in the way of
>> a release, I would be happy to assis
Hi,
I was wondering if there is currently a specific plan or list of
requirements to be fulfilled before the 1.0 of commons-csv is made.
For me personally, as well as (I think) other users of commons-csv, it
would be very useful to have a release as soon as possible -- even if
it is only to strea
