On 19 March 2013 18:38, Benedikt Ritter <brit...@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.c...@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 <brit...@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<dev-unsubscr...@commons.apache.org> >> For additional commands, e-mail: dev-h...@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-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
