You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Benedikt Ritter <br...@apache.org> on 2013/03/19 13:39:55 UTC
[CSV] Finishing v1.0
Hi all,
we have this request [1] from the Any23 community regarding [csv].
I believe we can help them in several ways.
The first thing to do would be to request a git mirror of [csv] from infra,
so that Any23 can use the latest trunk by cloning that mirror.
The second is to finish work on [csv] and push out a 1.0 soon.
When we were working on [csv] last year there were a few unresolved issues,
like improving performance and general refactoring. Also we have 6
unresolved bugs.
I'd like you to get involved in reviewing the state of the API.
Is the API in a state that can be shipped?
Does the API allow us to increase performances without breaking BC after
releasing 1.0.
My goal would be to fix the 6 open bugs and post pone improvements for 1.1.
People are waiting for this release (remember this issue with solr [2]?
They also want this library to be released!)
Who has some spare time to help me with this?
Regards,
Benedikt
[1] http://markmail.org/message/ylwdhkth2t2kjek4
[2] https://issues.apache.org/jira/browse/SOLR-3204
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Re: [CSV] Finishing v1.0
Posted by Adrian Crum <ad...@sandglass-software.com>.
Running mvn site generates an error:
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error during page generation
Embedded error: Error rendering Maven report: org.dom4j.DocumentFactory
cannot b
e cast to org.dom4j.DocumentFactory Nested exception:
org.dom4j.DocumentFactory
cannot be cast to org.dom4j.DocumentFactory
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
-Adrian
On 3/21/2013 9:38 AM, Adrian Crum wrote:
> The CSV site is very confusing:
>
> 1. The nightly build is not current.
> 2. The "JavaDoc (latest)" link points to an API that does not match
> the latest API.
>
> -Adrian
>
> On 3/20/2013 8:59 AM, Adrian Crum wrote:
>> Okay, that looks better.
>>
>> -Adrian
>>
>> On 3/20/2013 8:52 AM, Benedikt Ritter wrote:
>>> That build is dated 30-Jul-2007. Please have a look at trunk in SVN ;-)
>>>
>>> Benedikt
>>>
>>>
>>> 2013/3/20 Adrian Crum <ad...@sandglass-software.com>
>>>
>>>> I grabbed the latest build: http://people.apache.org/**
>>>> builds/commons/nightly/**commons-csv/<http://people.apache.org/builds/commons/nightly/commons-csv/>
>>>>
>>>>
>>>> -Adrian
>>>>
>>>>
>>>> On 3/20/2013 8:43 AM, Benedikt Ritter wrote:
>>>>
>>>>> Adrian, you've lost me. What CSVStrategy are you talking about?
>>>>> Are you
>>>>> looking at
>>>>> https://svn.apache.org/repos/**asf/commons/proper/csv/trunk<https://svn.apache.org/repos/asf/commons/proper/csv/trunk>?
>>>>>
>>>>>
>>>>> 2013/3/20 Adrian Crum
>>>>> <ad...@sandglass-software.com>
>>>>> There is a part of the API that I don't like - the CSVStrategy
>>>>> class is
>>>>>> mutable. I can't imagine a file's strategy changing mid-file, so
>>>>>> from my
>>>>>> perspective the class should be immutable. Plus, the previous
>>>>>> version
>>>>>> used
>>>>>> a builder pattern that I liked.
>>>>>>
>>>>>> -Adrian
>>>>>>
>>>>>>
>>>>>> On 3/19/2013 6:43 PM, sebb wrote:
>>>>>>
>>>>>> On 19 March 2013 18:38, Benedikt Ritter <br...@apache.org>
>>>>>> wrote:
>>>>>>> How do you feel about postponing some of the improvement
>>>>>>> tickets until
>>>>>>>> after the initial release? Is this possible with commons
>>>>>>>> release policy
>>>>>>>> or
>>>>>>>> do we have to resolve all open issues?
>>>>>>>>
>>>>>>>> As far as I'm concerned, Improvement tickets can be postponed.
>>>>>>> IMO the only items that must be fixed are regressions (not possible
>>>>>>> for first release of course).
>>>>>>> Also if there is new code with a bad API, that needs to be fixed
>>>>>>> before first release as it may be impossible to fix later without
>>>>>>> causing lots of trouble,
>>>>>>>
>>>>>>> Benedikt
>>>>>>>
>>>>>>>> 2013/3/19 Adrian Crum
>>>>>>>> <adrian.crum@sandglass-**softw**are.com<http://software.com>
>>>>>>>> <ad...@sandglass-software.com>
>>>>>>>>
>>>>>>>> I would be interested in helping too.
>>>>>>>>
>>>>>>>>> -Adrian
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>>>>>>>>>
>>>>>>>>> I am interested in seeing it through a 1.0. Let's make sure
>>>>>>>>> we like
>>>>>>>>> the
>>>>>>>>>
>>>>>>>>>> API...
>>>>>>>>>>
>>>>>>>>>> Gary
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter
>>>>>>>>>> <britter@apache.org
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> we have this request [1] from the Any23 community regarding
>>>>>>>>>> [csv].
>>>>>>>>>>> I believe we can help them in several ways.
>>>>>>>>>>> The first thing to do would be to request a git mirror of
>>>>>>>>>>> [csv] from
>>>>>>>>>>> infra,
>>>>>>>>>>> so that Any23 can use the latest trunk by cloning that mirror.
>>>>>>>>>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>>>>>>>>>
>>>>>>>>>>> When we were working on [csv] last year there were a few
>>>>>>>>>>> unresolved
>>>>>>>>>>> issues,
>>>>>>>>>>> like improving performance and general refactoring. Also we
>>>>>>>>>>> have 6
>>>>>>>>>>> unresolved bugs.
>>>>>>>>>>> I'd like you to get involved in reviewing the state of the API.
>>>>>>>>>>> Is the API in a state that can be shipped?
>>>>>>>>>>> Does the API allow us to increase performances without
>>>>>>>>>>> breaking BC
>>>>>>>>>>> after
>>>>>>>>>>> releasing 1.0.
>>>>>>>>>>>
>>>>>>>>>>> My goal would be to fix the 6 open bugs and post pone
>>>>>>>>>>> improvements
>>>>>>>>>>> for
>>>>>>>>>>> 1.1.
>>>>>>>>>>> People are waiting for this release (remember this issue
>>>>>>>>>>> with solr
>>>>>>>>>>> [2]?
>>>>>>>>>>> They also want this library to be released!)
>>>>>>>>>>> Who has some spare time to help me with this?
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Benedikt
>>>>>>>>>>>
>>>>>>>>>>> [1]
>>>>>>>>>>> http://markmail.org/message/******ylwdhkth2t2kjek4<http://markmail.org/message/****ylwdhkth2t2kjek4>
>>>>>>>>>>> <http://**markmail.org/message/****ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>>>>>>
>>>>>>>>>>> <http://**markmail.org/**message/**ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>>>>>>
>>>>>>>>>>> <htt**p://markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>>>>>>>>>>
>>>>>>>>>>> [2]
>>>>>>>>>>> https://issues.apache.org/******jira/browse/SOLR-3204<https://issues.apache.org/****jira/browse/SOLR-3204>
>>>>>>>>>>> <https://**issues.apache.org/**jira/**browse/SOLR-3204<https://issues.apache.org/**jira/browse/SOLR-3204>
>>>>>>>>>>>
>>>>>>>>>>> <https://**issues.apache.org/**jira/browse/**SOLR-3204<http://issues.apache.org/jira/browse/**SOLR-3204>
>>>>>>>>>>>
>>>>>>>>>>> <https:**//issues.apache.org/jira/**browse/SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> http://people.apache.org/~******britter/<http://people.apache.org/~****britter/>
>>>>>>>>>>>
>>>>>>>>>>> <http://people.apache.**org/~**britter/<http://people.apache.org/~**britter/>
>>>>>>>>>>>
>>>>>>>>>>> <http://people.apache.**org/~**britter/<http://people.apache.**
>>>>>>>>>>> org/~britter/ <http://people.apache.org/~britter/>>
>>>>>>>>>>> http://www.systemoutprintln.******de/
>>>>>>>>>>> <http://www.systemoutprintln.
>>>>>>>>>>> ****
>>>>>>>>>>> de/
>>>>>>>>>>> <http://www.systemoutprintln.**de/<http://www.systemoutprintln.de/>
>>>>>>>>>>> http://twitter.com/******BenediktRitter<http://twitter.com/****BenediktRitter>
>>>>>>>>>>>
>>>>>>>>>>> <http://twitter.**com/**BenediktRitter<http://twitter.com/**BenediktRitter>
>>>>>>>>>>>
>>>>>>>>>>>> <
>>>>>>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter>
>>>>>>>>>>>
>>>>>>>>>>> <http://twitter.**com/BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>>>>>>>
>>>>>>>>>>> http://github.com/britter
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------******--------------------------**
>>>>>>>>>>>
>>>>>>>>>> --**
>>>>>>>>>>
>>>>>>>>> --**---------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.****apac**he.org<
>>>>>>>>> http://apache.org**>
>>>>>>>>> <dev-unsubscribe@**commons.**apache.org
>>>>>>>>> <http://commons.apache.org><
>>>>>>>>> dev-unsubscribe@**commons.apache.org<de...@commons.apache.org>
>>>>>>>>>
>>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>> http://people.apache.org/~****britter/<http://people.apache.org/~**britter/>
>>>>>>>>
>>>>>>>> <http://people.apache.**org/~britter/<http://people.apache.org/~britter/>
>>>>>>>>
>>>>>>>> http://www.systemoutprintln.****de/
>>>>>>>> <http://www.systemoutprintln.**de/<http://www.systemoutprintln.de/>
>>>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter><
>>>>>>>>
>>>>>>>> http://twitter.com/**BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>>>>
>>>>>>>> http://github.com/britter
>>>>>>>>
>>>>>>>> ------------------------------****----------------------------**
>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail:
>>>>>>> dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>>>>> <de...@commons.apache.org>
>>>>>>>
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------****----------------------------**
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail:
>>>>>> dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>>>> <de...@commons.apache.org>
>>>>>>
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>> ------------------------------**------------------------------**---------
>>>>
>>>> To unsubscribe, e-mail:
>>>> dev-unsubscribe@commons.**apache.org<de...@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
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [CSV] Finishing v1.0
Posted by Adrian Crum <ad...@sandglass-software.com>.
The CSV site is very confusing:
1. The nightly build is not current.
2. The "JavaDoc (latest)" link points to an API that does not match the
latest API.
-Adrian
On 3/20/2013 8:59 AM, Adrian Crum wrote:
> Okay, that looks better.
>
> -Adrian
>
> On 3/20/2013 8:52 AM, Benedikt Ritter wrote:
>> That build is dated 30-Jul-2007. Please have a look at trunk in SVN ;-)
>>
>> Benedikt
>>
>>
>> 2013/3/20 Adrian Crum <ad...@sandglass-software.com>
>>
>>> I grabbed the latest build: http://people.apache.org/**
>>> builds/commons/nightly/**commons-csv/<http://people.apache.org/builds/commons/nightly/commons-csv/>
>>>
>>>
>>> -Adrian
>>>
>>>
>>> On 3/20/2013 8:43 AM, Benedikt Ritter wrote:
>>>
>>>> Adrian, you've lost me. What CSVStrategy are you talking about? Are
>>>> you
>>>> looking at
>>>> https://svn.apache.org/repos/**asf/commons/proper/csv/trunk<https://svn.apache.org/repos/asf/commons/proper/csv/trunk>?
>>>>
>>>>
>>>> 2013/3/20 Adrian Crum
>>>> <ad...@sandglass-software.com>
>>>> There is a part of the API that I don't like - the CSVStrategy
>>>> class is
>>>>> mutable. I can't imagine a file's strategy changing mid-file, so
>>>>> from my
>>>>> perspective the class should be immutable. Plus, the previous version
>>>>> used
>>>>> a builder pattern that I liked.
>>>>>
>>>>> -Adrian
>>>>>
>>>>>
>>>>> On 3/19/2013 6:43 PM, sebb wrote:
>>>>>
>>>>> On 19 March 2013 18:38, Benedikt Ritter <br...@apache.org> wrote:
>>>>>> How do you feel about postponing some of the improvement
>>>>>> tickets until
>>>>>>> after the initial release? Is this possible with commons release
>>>>>>> policy
>>>>>>> or
>>>>>>> do we have to resolve all open issues?
>>>>>>>
>>>>>>> As far as I'm concerned, Improvement tickets can be postponed.
>>>>>> IMO the only items that must be fixed are regressions (not possible
>>>>>> for first release of course).
>>>>>> Also if there is new code with a bad API, that needs to be fixed
>>>>>> before first release as it may be impossible to fix later without
>>>>>> causing lots of trouble,
>>>>>>
>>>>>> Benedikt
>>>>>>
>>>>>>> 2013/3/19 Adrian Crum
>>>>>>> <adrian.crum@sandglass-**softw**are.com<http://software.com>
>>>>>>> <ad...@sandglass-software.com>
>>>>>>>
>>>>>>> I would be interested in helping too.
>>>>>>>
>>>>>>>> -Adrian
>>>>>>>>
>>>>>>>>
>>>>>>>> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>>>>>>>>
>>>>>>>> I am interested in seeing it through a 1.0. Let's make sure
>>>>>>>> we like
>>>>>>>> the
>>>>>>>>
>>>>>>>>> API...
>>>>>>>>>
>>>>>>>>> Gary
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter
>>>>>>>>> <britter@apache.org
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi all,
>>>>>>>>>
>>>>>>>>> we have this request [1] from the Any23 community regarding
>>>>>>>>> [csv].
>>>>>>>>>> I believe we can help them in several ways.
>>>>>>>>>> The first thing to do would be to request a git mirror of
>>>>>>>>>> [csv] from
>>>>>>>>>> infra,
>>>>>>>>>> so that Any23 can use the latest trunk by cloning that mirror.
>>>>>>>>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>>>>>>>>
>>>>>>>>>> When we were working on [csv] last year there were a few
>>>>>>>>>> unresolved
>>>>>>>>>> issues,
>>>>>>>>>> like improving performance and general refactoring. Also we
>>>>>>>>>> have 6
>>>>>>>>>> unresolved bugs.
>>>>>>>>>> I'd like you to get involved in reviewing the state of the API.
>>>>>>>>>> Is the API in a state that can be shipped?
>>>>>>>>>> Does the API allow us to increase performances without
>>>>>>>>>> breaking BC
>>>>>>>>>> after
>>>>>>>>>> releasing 1.0.
>>>>>>>>>>
>>>>>>>>>> My goal would be to fix the 6 open bugs and post pone
>>>>>>>>>> improvements
>>>>>>>>>> for
>>>>>>>>>> 1.1.
>>>>>>>>>> People are waiting for this release (remember this issue with
>>>>>>>>>> solr
>>>>>>>>>> [2]?
>>>>>>>>>> They also want this library to be released!)
>>>>>>>>>> Who has some spare time to help me with this?
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Benedikt
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> http://markmail.org/message/******ylwdhkth2t2kjek4<http://markmail.org/message/****ylwdhkth2t2kjek4>
>>>>>>>>>> <http://**markmail.org/message/****ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>>>>>
>>>>>>>>>> <http://**markmail.org/**message/**ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>>>>>
>>>>>>>>>> <htt**p://markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>>>>>>>>>
>>>>>>>>>> [2]
>>>>>>>>>> https://issues.apache.org/******jira/browse/SOLR-3204<https://issues.apache.org/****jira/browse/SOLR-3204>
>>>>>>>>>> <https://**issues.apache.org/**jira/**browse/SOLR-3204<https://issues.apache.org/**jira/browse/SOLR-3204>
>>>>>>>>>>
>>>>>>>>>> <https://**issues.apache.org/**jira/browse/**SOLR-3204<http://issues.apache.org/jira/browse/**SOLR-3204>
>>>>>>>>>>
>>>>>>>>>> <https:**//issues.apache.org/jira/**browse/SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> http://people.apache.org/~******britter/<http://people.apache.org/~****britter/>
>>>>>>>>>>
>>>>>>>>>> <http://people.apache.**org/~**britter/<http://people.apache.org/~**britter/>
>>>>>>>>>>
>>>>>>>>>> <http://people.apache.**org/~**britter/<http://people.apache.**
>>>>>>>>>> org/~britter/ <http://people.apache.org/~britter/>>
>>>>>>>>>> http://www.systemoutprintln.******de/
>>>>>>>>>> <http://www.systemoutprintln.
>>>>>>>>>> ****
>>>>>>>>>> de/
>>>>>>>>>> <http://www.systemoutprintln.**de/<http://www.systemoutprintln.de/>
>>>>>>>>>> http://twitter.com/******BenediktRitter<http://twitter.com/****BenediktRitter>
>>>>>>>>>>
>>>>>>>>>> <http://twitter.**com/**BenediktRitter<http://twitter.com/**BenediktRitter>
>>>>>>>>>>
>>>>>>>>>>> <
>>>>>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter>
>>>>>>>>>>
>>>>>>>>>> <http://twitter.**com/BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>>>>>>
>>>>>>>>>> http://github.com/britter
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------******--------------------------**
>>>>>>>>> --**
>>>>>>>>>
>>>>>>>> --**---------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.****apac**he.org<
>>>>>>>> http://apache.org**>
>>>>>>>> <dev-unsubscribe@**commons.**apache.org
>>>>>>>> <http://commons.apache.org><
>>>>>>>> dev-unsubscribe@**commons.apache.org<de...@commons.apache.org>
>>>>>>>>
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>> http://people.apache.org/~****britter/<http://people.apache.org/~**britter/>
>>>>>>>
>>>>>>> <http://people.apache.**org/~britter/<http://people.apache.org/~britter/>
>>>>>>>
>>>>>>> http://www.systemoutprintln.****de/
>>>>>>> <http://www.systemoutprintln.**de/<http://www.systemoutprintln.de/>
>>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter><
>>>>>>>
>>>>>>> http://twitter.com/**BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>>>
>>>>>>> http://github.com/britter
>>>>>>>
>>>>>>> ------------------------------****----------------------------**
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail:
>>>>>> dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>>>> <de...@commons.apache.org>
>>>>>>
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>>
>>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail:
>>>>> dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>>> <de...@commons.apache.org>
>>>>>
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>>>
>>> ------------------------------**------------------------------**---------
>>>
>>> To unsubscribe, e-mail:
>>> dev-unsubscribe@commons.**apache.org<de...@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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [CSV] Finishing v1.0
Posted by Adrian Crum <ad...@sandglass-software.com>.
Okay, that looks better.
-Adrian
On 3/20/2013 8:52 AM, Benedikt Ritter wrote:
> That build is dated 30-Jul-2007. Please have a look at trunk in SVN ;-)
>
> Benedikt
>
>
> 2013/3/20 Adrian Crum <ad...@sandglass-software.com>
>
>> I grabbed the latest build: http://people.apache.org/**
>> builds/commons/nightly/**commons-csv/<http://people.apache.org/builds/commons/nightly/commons-csv/>
>>
>> -Adrian
>>
>>
>> On 3/20/2013 8:43 AM, Benedikt Ritter wrote:
>>
>>> Adrian, you've lost me. What CSVStrategy are you talking about? Are you
>>> looking at https://svn.apache.org/repos/**asf/commons/proper/csv/trunk<https://svn.apache.org/repos/asf/commons/proper/csv/trunk>?
>>>
>>>
>>> 2013/3/20 Adrian Crum <ad...@sandglass-software.com>
>>> There is a part of the API that I don't like - the CSVStrategy class is
>>>> mutable. I can't imagine a file's strategy changing mid-file, so from my
>>>> perspective the class should be immutable. Plus, the previous version
>>>> used
>>>> a builder pattern that I liked.
>>>>
>>>> -Adrian
>>>>
>>>>
>>>> On 3/19/2013 6:43 PM, sebb wrote:
>>>>
>>>> On 19 March 2013 18:38, Benedikt Ritter <br...@apache.org> wrote:
>>>>> How do you feel about postponing some of the improvement tickets until
>>>>>> after the initial release? Is this possible with commons release policy
>>>>>> or
>>>>>> do we have to resolve all open issues?
>>>>>>
>>>>>> As far as I'm concerned, Improvement tickets can be postponed.
>>>>> IMO the only items that must be fixed are regressions (not possible
>>>>> for first release of course).
>>>>> Also if there is new code with a bad API, that needs to be fixed
>>>>> before first release as it may be impossible to fix later without
>>>>> causing lots of trouble,
>>>>>
>>>>> Benedikt
>>>>>
>>>>>> 2013/3/19 Adrian Crum <adrian.crum@sandglass-**softw**are.com<http://software.com>
>>>>>> <ad...@sandglass-software.com>
>>>>>> I would be interested in helping too.
>>>>>>
>>>>>>> -Adrian
>>>>>>>
>>>>>>>
>>>>>>> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>>>>>>>
>>>>>>> I am interested in seeing it through a 1.0. Let's make sure we like
>>>>>>> the
>>>>>>>
>>>>>>>> API...
>>>>>>>>
>>>>>>>> Gary
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <britter@apache.org
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> we have this request [1] from the Any23 community regarding [csv].
>>>>>>>>> I believe we can help them in several ways.
>>>>>>>>> The first thing to do would be to request a git mirror of [csv] from
>>>>>>>>> infra,
>>>>>>>>> so that Any23 can use the latest trunk by cloning that mirror.
>>>>>>>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>>>>>>>
>>>>>>>>> When we were working on [csv] last year there were a few unresolved
>>>>>>>>> issues,
>>>>>>>>> like improving performance and general refactoring. Also we have 6
>>>>>>>>> unresolved bugs.
>>>>>>>>> I'd like you to get involved in reviewing the state of the API.
>>>>>>>>> Is the API in a state that can be shipped?
>>>>>>>>> Does the API allow us to increase performances without breaking BC
>>>>>>>>> after
>>>>>>>>> releasing 1.0.
>>>>>>>>>
>>>>>>>>> My goal would be to fix the 6 open bugs and post pone improvements
>>>>>>>>> for
>>>>>>>>> 1.1.
>>>>>>>>> People are waiting for this release (remember this issue with solr
>>>>>>>>> [2]?
>>>>>>>>> They also want this library to be released!)
>>>>>>>>> Who has some spare time to help me with this?
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Benedikt
>>>>>>>>>
>>>>>>>>> [1] http://markmail.org/message/******ylwdhkth2t2kjek4<http://markmail.org/message/****ylwdhkth2t2kjek4>
>>>>>>>>> <http://**markmail.org/message/****ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>>>> <http://**markmail.org/**message/**ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>>>> <htt**p://markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>>>>>>>> [2] https://issues.apache.org/******jira/browse/SOLR-3204<https://issues.apache.org/****jira/browse/SOLR-3204>
>>>>>>>>> <https://**issues.apache.org/**jira/**browse/SOLR-3204<https://issues.apache.org/**jira/browse/SOLR-3204>
>>>>>>>>> <https://**issues.apache.org/**jira/browse/**SOLR-3204<http://issues.apache.org/jira/browse/**SOLR-3204>
>>>>>>>>> <https:**//issues.apache.org/jira/**browse/SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>>>>>>>> --
>>>>>>>>> http://people.apache.org/~******britter/<http://people.apache.org/~****britter/>
>>>>>>>>> <http://people.apache.**org/~**britter/<http://people.apache.org/~**britter/>
>>>>>>>>> <http://people.apache.**org/~**britter/<http://people.apache.**
>>>>>>>>> org/~britter/ <http://people.apache.org/~britter/>>
>>>>>>>>> http://www.systemoutprintln.******de/ <http://www.systemoutprintln.
>>>>>>>>> ****
>>>>>>>>> de/ <http://www.systemoutprintln.**de/<http://www.systemoutprintln.de/>
>>>>>>>>> http://twitter.com/******BenediktRitter<http://twitter.com/****BenediktRitter>
>>>>>>>>> <http://twitter.**com/**BenediktRitter<http://twitter.com/**BenediktRitter>
>>>>>>>>>> <
>>>>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter>
>>>>>>>>> <http://twitter.**com/BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>>>>> http://github.com/britter
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------******--------------------------**
>>>>>>>> --**
>>>>>>>>
>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.****apac**he.org<
>>>>>>> http://apache.org**>
>>>>>>> <dev-unsubscribe@**commons.**apache.org <http://commons.apache.org><
>>>>>>> dev-unsubscribe@**commons.apache.org<de...@commons.apache.org>
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>> http://people.apache.org/~****britter/<http://people.apache.org/~**britter/>
>>>>>> <http://people.apache.**org/~britter/<http://people.apache.org/~britter/>
>>>>>> http://www.systemoutprintln.****de/ <http://www.systemoutprintln.**de/<http://www.systemoutprintln.de/>
>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter><
>>>>>> http://twitter.com/**BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>> http://github.com/britter
>>>>>>
>>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>>> <de...@commons.apache.org>
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>> <de...@commons.apache.org>
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@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: [CSV] Finishing v1.0
Posted by Benedikt Ritter <br...@apache.org>.
That build is dated 30-Jul-2007. Please have a look at trunk in SVN ;-)
Benedikt
2013/3/20 Adrian Crum <ad...@sandglass-software.com>
> I grabbed the latest build: http://people.apache.org/**
> builds/commons/nightly/**commons-csv/<http://people.apache.org/builds/commons/nightly/commons-csv/>
>
> -Adrian
>
>
> On 3/20/2013 8:43 AM, Benedikt Ritter wrote:
>
>> Adrian, you've lost me. What CSVStrategy are you talking about? Are you
>> looking at https://svn.apache.org/repos/**asf/commons/proper/csv/trunk<https://svn.apache.org/repos/asf/commons/proper/csv/trunk>?
>>
>>
>> 2013/3/20 Adrian Crum <ad...@sandglass-software.com>
>> >
>>
>> There is a part of the API that I don't like - the CSVStrategy class is
>>> mutable. I can't imagine a file's strategy changing mid-file, so from my
>>> perspective the class should be immutable. Plus, the previous version
>>> used
>>> a builder pattern that I liked.
>>>
>>> -Adrian
>>>
>>>
>>> On 3/19/2013 6:43 PM, sebb wrote:
>>>
>>> On 19 March 2013 18:38, Benedikt Ritter <br...@apache.org> wrote:
>>>>
>>>> How do you feel about postponing some of the improvement tickets until
>>>>> after the initial release? Is this possible with commons release policy
>>>>> or
>>>>> do we have to resolve all open issues?
>>>>>
>>>>> As far as I'm concerned, Improvement tickets can be postponed.
>>>>
>>>> IMO the only items that must be fixed are regressions (not possible
>>>> for first release of course).
>>>> Also if there is new code with a bad API, that needs to be fixed
>>>> before first release as it may be impossible to fix later without
>>>> causing lots of trouble,
>>>>
>>>> Benedikt
>>>>
>>>>>
>>>>> 2013/3/19 Adrian Crum <adrian.crum@sandglass-**softw**are.com<http://software.com>
>>>>> <ad...@sandglass-software.com>
>>>>> >
>>>>>
>>>>> I would be interested in helping too.
>>>>>
>>>>>> -Adrian
>>>>>>
>>>>>>
>>>>>> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>>>>>>
>>>>>> I am interested in seeing it through a 1.0. Let's make sure we like
>>>>>> the
>>>>>>
>>>>>>> API...
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <britter@apache.org
>>>>>>> >
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> we have this request [1] from the Any23 community regarding [csv].
>>>>>>>> I believe we can help them in several ways.
>>>>>>>> The first thing to do would be to request a git mirror of [csv] from
>>>>>>>> infra,
>>>>>>>> so that Any23 can use the latest trunk by cloning that mirror.
>>>>>>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>>>>>>
>>>>>>>> When we were working on [csv] last year there were a few unresolved
>>>>>>>> issues,
>>>>>>>> like improving performance and general refactoring. Also we have 6
>>>>>>>> unresolved bugs.
>>>>>>>> I'd like you to get involved in reviewing the state of the API.
>>>>>>>> Is the API in a state that can be shipped?
>>>>>>>> Does the API allow us to increase performances without breaking BC
>>>>>>>> after
>>>>>>>> releasing 1.0.
>>>>>>>>
>>>>>>>> My goal would be to fix the 6 open bugs and post pone improvements
>>>>>>>> for
>>>>>>>> 1.1.
>>>>>>>> People are waiting for this release (remember this issue with solr
>>>>>>>> [2]?
>>>>>>>> They also want this library to be released!)
>>>>>>>> Who has some spare time to help me with this?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Benedikt
>>>>>>>>
>>>>>>>> [1] http://markmail.org/message/******ylwdhkth2t2kjek4<http://markmail.org/message/****ylwdhkth2t2kjek4>
>>>>>>>> <http://**markmail.org/message/****ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>>> >
>>>>>>>> <http://**markmail.org/**message/**ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>>> <htt**p://markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>>>>>>> >
>>>>>>>> [2] https://issues.apache.org/******jira/browse/SOLR-3204<https://issues.apache.org/****jira/browse/SOLR-3204>
>>>>>>>> <https://**issues.apache.org/**jira/**browse/SOLR-3204<https://issues.apache.org/**jira/browse/SOLR-3204>
>>>>>>>> >
>>>>>>>> <https://**issues.apache.org/**jira/browse/**SOLR-3204<http://issues.apache.org/jira/browse/**SOLR-3204>
>>>>>>>> <https:**//issues.apache.org/jira/**browse/SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>>>>>>> >
>>>>>>>> --
>>>>>>>> http://people.apache.org/~******britter/<http://people.apache.org/~****britter/>
>>>>>>>> <http://people.apache.**org/~**britter/<http://people.apache.org/~**britter/>
>>>>>>>> >
>>>>>>>> <http://people.apache.**org/~**britter/<http://people.apache.**
>>>>>>>> org/~britter/ <http://people.apache.org/~britter/>>
>>>>>>>> http://www.systemoutprintln.******de/ <http://www.systemoutprintln.
>>>>>>>> ****
>>>>>>>> de/ <http://www.systemoutprintln.**de/<http://www.systemoutprintln.de/>
>>>>>>>> >>
>>>>>>>> http://twitter.com/******BenediktRitter<http://twitter.com/****BenediktRitter>
>>>>>>>> <http://twitter.**com/**BenediktRitter<http://twitter.com/**BenediktRitter>
>>>>>>>> ><
>>>>>>>>
>>>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter>
>>>>>>>> <http://twitter.**com/BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>>>> >
>>>>>>>> http://github.com/britter
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------******--------------------------**
>>>>>>> --**
>>>>>>>
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.****apac**he.org<
>>>>>> http://apache.org**>
>>>>>> <dev-unsubscribe@**commons.**apache.org <http://commons.apache.org><
>>>>>> dev-unsubscribe@**commons.apache.org<de...@commons.apache.org>
>>>>>> >
>>>>>>
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>> http://people.apache.org/~****britter/<http://people.apache.org/~**britter/>
>>>>> <http://people.apache.**org/~britter/<http://people.apache.org/~britter/>
>>>>> >
>>>>> http://www.systemoutprintln.****de/ <http://www.systemoutprintln.**de/<http://www.systemoutprintln.de/>
>>>>> >
>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter><
>>>>> http://twitter.com/**BenediktRitter<http://twitter.com/BenediktRitter>
>>>>> >
>>>>> http://github.com/britter
>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>> <de...@commons.apache.org>
>>>> >
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>> <de...@commons.apache.org>
>>> >
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Re: [CSV] Finishing v1.0
Posted by Adrian Crum <ad...@sandglass-software.com>.
I grabbed the latest build:
http://people.apache.org/builds/commons/nightly/commons-csv/
-Adrian
On 3/20/2013 8:43 AM, Benedikt Ritter wrote:
> Adrian, you've lost me. What CSVStrategy are you talking about? Are you
> looking at https://svn.apache.org/repos/asf/commons/proper/csv/trunk ?
>
>
> 2013/3/20 Adrian Crum <ad...@sandglass-software.com>
>
>> There is a part of the API that I don't like - the CSVStrategy class is
>> mutable. I can't imagine a file's strategy changing mid-file, so from my
>> perspective the class should be immutable. Plus, the previous version used
>> a builder pattern that I liked.
>>
>> -Adrian
>>
>>
>> On 3/19/2013 6:43 PM, sebb wrote:
>>
>>> On 19 March 2013 18:38, Benedikt Ritter <br...@apache.org> wrote:
>>>
>>>> How do you feel about postponing some of the improvement tickets until
>>>> after the initial release? Is this possible with commons release policy
>>>> or
>>>> do we have to resolve all open issues?
>>>>
>>> As far as I'm concerned, Improvement tickets can be postponed.
>>>
>>> IMO the only items that must be fixed are regressions (not possible
>>> for first release of course).
>>> Also if there is new code with a bad API, that needs to be fixed
>>> before first release as it may be impossible to fix later without
>>> causing lots of trouble,
>>>
>>> Benedikt
>>>>
>>>> 2013/3/19 Adrian Crum <ad...@sandglass-software.com>
>>>> I would be interested in helping too.
>>>>> -Adrian
>>>>>
>>>>>
>>>>> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>>>>>
>>>>> I am interested in seeing it through a 1.0. Let's make sure we like the
>>>>>> API...
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>>
>>>>>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <br...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>>> we have this request [1] from the Any23 community regarding [csv].
>>>>>>> I believe we can help them in several ways.
>>>>>>> The first thing to do would be to request a git mirror of [csv] from
>>>>>>> infra,
>>>>>>> so that Any23 can use the latest trunk by cloning that mirror.
>>>>>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>>>>>
>>>>>>> When we were working on [csv] last year there were a few unresolved
>>>>>>> issues,
>>>>>>> like improving performance and general refactoring. Also we have 6
>>>>>>> unresolved bugs.
>>>>>>> I'd like you to get involved in reviewing the state of the API.
>>>>>>> Is the API in a state that can be shipped?
>>>>>>> Does the API allow us to increase performances without breaking BC
>>>>>>> after
>>>>>>> releasing 1.0.
>>>>>>>
>>>>>>> My goal would be to fix the 6 open bugs and post pone improvements for
>>>>>>> 1.1.
>>>>>>> People are waiting for this release (remember this issue with solr
>>>>>>> [2]?
>>>>>>> They also want this library to be released!)
>>>>>>> Who has some spare time to help me with this?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Benedikt
>>>>>>>
>>>>>>> [1] http://markmail.org/message/****ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>>> <http://**markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>>>>>> [2] https://issues.apache.org/****jira/browse/SOLR-3204<https://issues.apache.org/**jira/browse/SOLR-3204>
>>>>>>> <https://**issues.apache.org/jira/browse/**SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>>>>>> --
>>>>>>> http://people.apache.org/~****britter/<http://people.apache.org/~**britter/>
>>>>>>> <http://people.apache.**org/~britter/<http://people.apache.org/~britter/>
>>>>>>> http://www.systemoutprintln.****de/ <http://www.systemoutprintln.**
>>>>>>> de/ <http://www.systemoutprintln.de/>>
>>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter><
>>>>>>> http://twitter.com/**BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>>> http://github.com/britter
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>>> <de...@commons.apache.org>
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>>
>>>>>
>>>> --
>>>> http://people.apache.org/~**britter/<http://people.apache.org/~britter/>
>>>> http://www.systemoutprintln.**de/ <http://www.systemoutprintln.de/>
>>>> http://twitter.com/**BenediktRitter <http://twitter.com/BenediktRitter>
>>>> http://github.com/britter
>>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@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: [CSV] Finishing v1.0
Posted by Benedikt Ritter <br...@apache.org>.
Adrian, you've lost me. What CSVStrategy are you talking about? Are you
looking at https://svn.apache.org/repos/asf/commons/proper/csv/trunk ?
2013/3/20 Adrian Crum <ad...@sandglass-software.com>
> There is a part of the API that I don't like - the CSVStrategy class is
> mutable. I can't imagine a file's strategy changing mid-file, so from my
> perspective the class should be immutable. Plus, the previous version used
> a builder pattern that I liked.
>
> -Adrian
>
>
> On 3/19/2013 6:43 PM, sebb wrote:
>
>> On 19 March 2013 18:38, Benedikt Ritter <br...@apache.org> wrote:
>>
>>> How do you feel about postponing some of the improvement tickets until
>>> after the initial release? Is this possible with commons release policy
>>> or
>>> do we have to resolve all open issues?
>>>
>> As far as I'm concerned, Improvement tickets can be postponed.
>>
>> IMO the only items that must be fixed are regressions (not possible
>> for first release of course).
>> Also if there is new code with a bad API, that needs to be fixed
>> before first release as it may be impossible to fix later without
>> causing lots of trouble,
>>
>> Benedikt
>>>
>>>
>>> 2013/3/19 Adrian Crum <ad...@sandglass-software.com>
>>> >
>>>
>>> I would be interested in helping too.
>>>>
>>>> -Adrian
>>>>
>>>>
>>>> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>>>>
>>>> I am interested in seeing it through a 1.0. Let's make sure we like the
>>>>> API...
>>>>>
>>>>> Gary
>>>>>
>>>>>
>>>>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <br...@apache.org>
>>>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>>> we have this request [1] from the Any23 community regarding [csv].
>>>>>> I believe we can help them in several ways.
>>>>>> The first thing to do would be to request a git mirror of [csv] from
>>>>>> infra,
>>>>>> so that Any23 can use the latest trunk by cloning that mirror.
>>>>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>>>>
>>>>>> When we were working on [csv] last year there were a few unresolved
>>>>>> issues,
>>>>>> like improving performance and general refactoring. Also we have 6
>>>>>> unresolved bugs.
>>>>>> I'd like you to get involved in reviewing the state of the API.
>>>>>> Is the API in a state that can be shipped?
>>>>>> Does the API allow us to increase performances without breaking BC
>>>>>> after
>>>>>> releasing 1.0.
>>>>>>
>>>>>> My goal would be to fix the 6 open bugs and post pone improvements for
>>>>>> 1.1.
>>>>>> People are waiting for this release (remember this issue with solr
>>>>>> [2]?
>>>>>> They also want this library to be released!)
>>>>>> Who has some spare time to help me with this?
>>>>>>
>>>>>> Regards,
>>>>>> Benedikt
>>>>>>
>>>>>> [1] http://markmail.org/message/****ylwdhkth2t2kjek4<http://markmail.org/message/**ylwdhkth2t2kjek4>
>>>>>> <http://**markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>>>>> >
>>>>>> [2] https://issues.apache.org/****jira/browse/SOLR-3204<https://issues.apache.org/**jira/browse/SOLR-3204>
>>>>>> <https://**issues.apache.org/jira/browse/**SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>>>>> >
>>>>>> --
>>>>>> http://people.apache.org/~****britter/<http://people.apache.org/~**britter/>
>>>>>> <http://people.apache.**org/~britter/<http://people.apache.org/~britter/>
>>>>>> >
>>>>>> http://www.systemoutprintln.****de/ <http://www.systemoutprintln.**
>>>>>> de/ <http://www.systemoutprintln.de/>>
>>>>>> http://twitter.com/****BenediktRitter<http://twitter.com/**BenediktRitter><
>>>>>> http://twitter.com/**BenediktRitter<http://twitter.com/BenediktRitter>
>>>>>> >
>>>>>> http://github.com/britter
>>>>>>
>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apac**he.org<http://apache.org>
>>>> <de...@commons.apache.org>
>>>> >
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>>
>>> --
>>> http://people.apache.org/~**britter/<http://people.apache.org/~britter/>
>>> http://www.systemoutprintln.**de/ <http://www.systemoutprintln.de/>
>>> http://twitter.com/**BenediktRitter <http://twitter.com/BenediktRitter>
>>> http://github.com/britter
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Re: [CSV] Finishing v1.0
Posted by Adrian Crum <ad...@sandglass-software.com>.
There is a part of the API that I don't like - the CSVStrategy class is
mutable. I can't imagine a file's strategy changing mid-file, so from my
perspective the class should be immutable. Plus, the previous version
used a builder pattern that I liked.
-Adrian
On 3/19/2013 6:43 PM, sebb wrote:
> On 19 March 2013 18:38, Benedikt Ritter <br...@apache.org> wrote:
>> How do you feel about postponing some of the improvement tickets until
>> after the initial release? Is this possible with commons release policy or
>> do we have to resolve all open issues?
> As far as I'm concerned, Improvement tickets can be postponed.
>
> IMO the only items that must be fixed are regressions (not possible
> for first release of course).
> Also if there is new code with a bad API, that needs to be fixed
> before first release as it may be impossible to fix later without
> causing lots of trouble,
>
>> Benedikt
>>
>>
>> 2013/3/19 Adrian Crum <ad...@sandglass-software.com>
>>
>>> I would be interested in helping too.
>>>
>>> -Adrian
>>>
>>>
>>> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>>>
>>>> I am interested in seeing it through a 1.0. Let's make sure we like the
>>>> API...
>>>>
>>>> Gary
>>>>
>>>>
>>>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <br...@apache.org>
>>>> wrote:
>>>>
>>>> Hi all,
>>>>> we have this request [1] from the Any23 community regarding [csv].
>>>>> I believe we can help them in several ways.
>>>>> The first thing to do would be to request a git mirror of [csv] from
>>>>> infra,
>>>>> so that Any23 can use the latest trunk by cloning that mirror.
>>>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>>>
>>>>> When we were working on [csv] last year there were a few unresolved
>>>>> issues,
>>>>> like improving performance and general refactoring. Also we have 6
>>>>> unresolved bugs.
>>>>> I'd like you to get involved in reviewing the state of the API.
>>>>> Is the API in a state that can be shipped?
>>>>> Does the API allow us to increase performances without breaking BC after
>>>>> releasing 1.0.
>>>>>
>>>>> My goal would be to fix the 6 open bugs and post pone improvements for
>>>>> 1.1.
>>>>> People are waiting for this release (remember this issue with solr [2]?
>>>>> They also want this library to be released!)
>>>>> Who has some spare time to help me with this?
>>>>>
>>>>> Regards,
>>>>> Benedikt
>>>>>
>>>>> [1] http://markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>>>> [2] https://issues.apache.org/**jira/browse/SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>>>> --
>>>>> http://people.apache.org/~**britter/<http://people.apache.org/~britter/>
>>>>> http://www.systemoutprintln.**de/ <http://www.systemoutprintln.de/>
>>>>> http://twitter.com/**BenediktRitter <http://twitter.com/BenediktRitter>
>>>>> http://github.com/britter
>>>>>
>>>>>
>>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
> ---------------------------------------------------------------------
> 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: [CSV] Finishing v1.0
Posted by sebb <se...@gmail.com>.
On 19 March 2013 18:38, Benedikt Ritter <br...@apache.org> wrote:
> How do you feel about postponing some of the improvement tickets until
> after the initial release? Is this possible with commons release policy or
> do we have to resolve all open issues?
As far as I'm concerned, Improvement tickets can be postponed.
IMO the only items that must be fixed are regressions (not possible
for first release of course).
Also if there is new code with a bad API, that needs to be fixed
before first release as it may be impossible to fix later without
causing lots of trouble,
> Benedikt
>
>
> 2013/3/19 Adrian Crum <ad...@sandglass-software.com>
>
>> I would be interested in helping too.
>>
>> -Adrian
>>
>>
>> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>>
>>> I am interested in seeing it through a 1.0. Let's make sure we like the
>>> API...
>>>
>>> Gary
>>>
>>>
>>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <br...@apache.org>
>>> wrote:
>>>
>>> Hi all,
>>>>
>>>> we have this request [1] from the Any23 community regarding [csv].
>>>> I believe we can help them in several ways.
>>>> The first thing to do would be to request a git mirror of [csv] from
>>>> infra,
>>>> so that Any23 can use the latest trunk by cloning that mirror.
>>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>>
>>>> When we were working on [csv] last year there were a few unresolved
>>>> issues,
>>>> like improving performance and general refactoring. Also we have 6
>>>> unresolved bugs.
>>>> I'd like you to get involved in reviewing the state of the API.
>>>> Is the API in a state that can be shipped?
>>>> Does the API allow us to increase performances without breaking BC after
>>>> releasing 1.0.
>>>>
>>>> My goal would be to fix the 6 open bugs and post pone improvements for
>>>> 1.1.
>>>> People are waiting for this release (remember this issue with solr [2]?
>>>> They also want this library to be released!)
>>>> Who has some spare time to help me with this?
>>>>
>>>> Regards,
>>>> Benedikt
>>>>
>>>> [1] http://markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>>> [2] https://issues.apache.org/**jira/browse/SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>>> --
>>>> http://people.apache.org/~**britter/<http://people.apache.org/~britter/>
>>>> http://www.systemoutprintln.**de/ <http://www.systemoutprintln.de/>
>>>> http://twitter.com/**BenediktRitter <http://twitter.com/BenediktRitter>
>>>> http://github.com/britter
>>>>
>>>>
>>>
>>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [CSV] Finishing v1.0
Posted by Benedikt Ritter <br...@apache.org>.
How do you feel about postponing some of the improvement tickets until
after the initial release? Is this possible with commons release policy or
do we have to resolve all open issues?
Benedikt
2013/3/19 Adrian Crum <ad...@sandglass-software.com>
> I would be interested in helping too.
>
> -Adrian
>
>
> On 3/19/2013 12:53 PM, Gary Gregory wrote:
>
>> I am interested in seeing it through a 1.0. Let's make sure we like the
>> API...
>>
>> Gary
>>
>>
>> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <br...@apache.org>
>> wrote:
>>
>> Hi all,
>>>
>>> we have this request [1] from the Any23 community regarding [csv].
>>> I believe we can help them in several ways.
>>> The first thing to do would be to request a git mirror of [csv] from
>>> infra,
>>> so that Any23 can use the latest trunk by cloning that mirror.
>>> The second is to finish work on [csv] and push out a 1.0 soon.
>>>
>>> When we were working on [csv] last year there were a few unresolved
>>> issues,
>>> like improving performance and general refactoring. Also we have 6
>>> unresolved bugs.
>>> I'd like you to get involved in reviewing the state of the API.
>>> Is the API in a state that can be shipped?
>>> Does the API allow us to increase performances without breaking BC after
>>> releasing 1.0.
>>>
>>> My goal would be to fix the 6 open bugs and post pone improvements for
>>> 1.1.
>>> People are waiting for this release (remember this issue with solr [2]?
>>> They also want this library to be released!)
>>> Who has some spare time to help me with this?
>>>
>>> Regards,
>>> Benedikt
>>>
>>> [1] http://markmail.org/message/**ylwdhkth2t2kjek4<http://markmail.org/message/ylwdhkth2t2kjek4>
>>> [2] https://issues.apache.org/**jira/browse/SOLR-3204<https://issues.apache.org/jira/browse/SOLR-3204>
>>> --
>>> http://people.apache.org/~**britter/<http://people.apache.org/~britter/>
>>> http://www.systemoutprintln.**de/ <http://www.systemoutprintln.de/>
>>> http://twitter.com/**BenediktRitter <http://twitter.com/BenediktRitter>
>>> http://github.com/britter
>>>
>>>
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**apache.org<de...@commons.apache.org>
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Re: [CSV] Finishing v1.0
Posted by Adrian Crum <ad...@sandglass-software.com>.
I would be interested in helping too.
-Adrian
On 3/19/2013 12:53 PM, Gary Gregory wrote:
> I am interested in seeing it through a 1.0. Let's make sure we like the
> API...
>
> Gary
>
>
> On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <br...@apache.org> wrote:
>
>> Hi all,
>>
>> we have this request [1] from the Any23 community regarding [csv].
>> I believe we can help them in several ways.
>> The first thing to do would be to request a git mirror of [csv] from infra,
>> so that Any23 can use the latest trunk by cloning that mirror.
>> The second is to finish work on [csv] and push out a 1.0 soon.
>>
>> When we were working on [csv] last year there were a few unresolved issues,
>> like improving performance and general refactoring. Also we have 6
>> unresolved bugs.
>> I'd like you to get involved in reviewing the state of the API.
>> Is the API in a state that can be shipped?
>> Does the API allow us to increase performances without breaking BC after
>> releasing 1.0.
>>
>> My goal would be to fix the 6 open bugs and post pone improvements for 1.1.
>> People are waiting for this release (remember this issue with solr [2]?
>> They also want this library to be released!)
>> Who has some spare time to help me with this?
>>
>> Regards,
>> Benedikt
>>
>> [1] http://markmail.org/message/ylwdhkth2t2kjek4
>> [2] https://issues.apache.org/jira/browse/SOLR-3204
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [CSV] Finishing v1.0
Posted by Gary Gregory <ga...@gmail.com>.
I am interested in seeing it through a 1.0. Let's make sure we like the
API...
Gary
On Tue, Mar 19, 2013 at 8:39 AM, Benedikt Ritter <br...@apache.org> wrote:
> Hi all,
>
> we have this request [1] from the Any23 community regarding [csv].
> I believe we can help them in several ways.
> The first thing to do would be to request a git mirror of [csv] from infra,
> so that Any23 can use the latest trunk by cloning that mirror.
> The second is to finish work on [csv] and push out a 1.0 soon.
>
> When we were working on [csv] last year there were a few unresolved issues,
> like improving performance and general refactoring. Also we have 6
> unresolved bugs.
> I'd like you to get involved in reviewing the state of the API.
> Is the API in a state that can be shipped?
> Does the API allow us to increase performances without breaking BC after
> releasing 1.0.
>
> My goal would be to fix the 6 open bugs and post pone improvements for 1.1.
> People are waiting for this release (remember this issue with solr [2]?
> They also want this library to be released!)
> Who has some spare time to help me with this?
>
> Regards,
> Benedikt
>
> [1] http://markmail.org/message/ylwdhkth2t2kjek4
> [2] https://issues.apache.org/jira/browse/SOLR-3204
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory