Hi Yi, For the server part there are also some tasks in progress which we would get finished for the first release.
I would prefer to go forward with all that work (finish feature development and release preparation [1]). Lets say end of July we can discuss again if code is good enough for making a first release. I see also the option to postpone unfinished feature to the next release after the first one. And I would have no concerns to do this next release just a few weeks later. Release earlier and often. From my experience the making of a first release is effort due to the release policies by Apache [2]. If all policies are applied then the follow up release are easier to do. WDYT? Regards, Stephan [1] https://issues.apache.org/jira/browse/OLINGO-342 [2] http://www.apache.org/dev/release.html On 07.07.14 17:09, "Yi Ding" <[email protected]> wrote: >Hi Stephan, > >We are currently working with Francesco Chicchiriccò ><[email protected]> on some Java client improvements and we'll have >several major check-ins in July and first half of August. According to >this timeline, do you think if the improvements can make the date of this >first V4 release? > >Best, >Yi > >-----Original Message----- >From: Klevenz, Stephan [mailto:[email protected]] >Sent: Monday, July 7, 2014 3:45 PM >To: [email protected] >Subject: Re: [DISCUSS] OData 4.0 / making the first release > >I have created a Jira issue: > >https://issues.apache.org/jira/browse/OLINGO-342 > >For details I suggest just to create sub tasks for the issues. > >-- Stephan > >On 07.07.14 09:40, "Klevenz, Stephan" <[email protected]> wrote: > >>Hi Vikram, >> >>Thanks for showing interest into our OData 4.0 effort. The release date >>is ASAP. Actually it means there are some Apache specific issues we >>have to address an then fix first. I am going to open an issue for the >>release and there you can track progress. >> >>Feature side the server part will support a basic read scenario (read >>entry, read feed). The client api is more complete. >> >>Regards, >>Stephan >> >>On 07.07.14 06:42, "Vikram Pancholi" <[email protected]> wrote: >> >>>Hi, >>> I am new bee in the group. Plan for first release of V4 is a very >>>good news for me. My vote is +1. Looking forward to contribute in this >>>release. >>>Couple of things I would like to know a) tentative target date, b) >>>tentative list of features we target (already completed and in >>>pipeline.) >>> >>>Regards, >>>Vikram >>> >>> >>> >>>On Fri, Jul 4, 2014 at 1:59 PM, Bolz, Michael <[email protected]> >>>wrote: >>> >>>> Hi, >>>> >>>> I agree (and give +1) for a first release with version number "0.1.0". >>>> The only point I have to mention is that for support of basic read I >>>>want to resolve my issue (OLINGO-317) and merge it finally into the >>>>master branch. >>>> I'am confident that this will happen during next week (at least the >>>>final "master" merge). >>>> >>>> Kind regards, >>>> Michael >>>> >>>> >>>> >>>> >>>> >>>> On 04.07.14 09:49, "Klevenz, Stephan" <[email protected]> wrote: >>>> >>>> >Hi, >>>> > >>>> >I want to start another discussion about making the first release >>>> >for OData 4.0. >>>> > >>>> >The client code is in a good shape and also the server code is >>>> >nearly ready to support a basic read scenario for feeds and >>>> >entries. Because >>>>of >>>> >it is the first release there are quite a lot of things to do and I >>>>just >>>> >will summarize what came into my mind: >>>> > >>>> > * define a distribution set (zip files to be placed on download >>>>page) >>>> > * client java distribution (client jars + dependencies) >>>> > * client android distribution (I assume we need this?) >>>> > * server distribution (server jars + dependencies) >>>> > * maintain license and notice files >>>> > * refactor web pages (http://olingo.apache.org) >>>> > * OData 2.0 4.0 >>>> > * Java, Javascript download pages + documentation >>>> > * The current version number is 0.1.0-SNAPSHOT thus release >>>>version >>>> >will be 0.1.0. Is that ok? >>>> > >>>> >Are there other things we have to do? >>>> > >>>> >If you also think it is time to start with release effort then I >>>> >will create a Jira issue for that and we can assign sub tasks for >>>> >the >>>>details. >>>> > >>>> >Regards, >>>> >Stephan >> >
