Same. S.
On Dec 16, 2010, at 12:26 PM, Florent Guillaume wrote: > Hi, > > I'm ok for a 0.2.0. > > Florent > > > On Thu, Dec 16, 2010 at 12:17 PM, Gabriele Columbro <colum...@gmail.com> > wrote: >> Hey guys, >> I think it's about time to start the release procedure if we're still >> targeting to have this out by the end of the year. >> >> I volunteer to perform the release and I might be able to give it a shot >> tomorrow or over the weekend. >> >> Anything blocking this that you're aware of? If not, and case you have >> still code to be checked in, I'd ask you do it by tomorrow morning. >> >> WDYT? Everyone agrees that 0.2.0 is the proper meaningful version for this >> release? >> >> HTH, >> Gab >> >> On Dec 8, 2010, at 9:59 AM, Jens Hübel wrote: >> >>> Perhaps a good opportunity to ask the community again for a suitable >>> release date. >>> >>> From my side nothing should prevent us to push a release soon. We have >>> several gaps in the documentation that we need to fix but this should not be >>> a show stopper. How about the client library? >>> >>> Any suggestions? Is end of this year still valid? >>> >>> @Debbie: Great to hear that you made progress. Be aware that there were >>> some recent changes with exception handling and that there is currently no >>> full-text support in our grammar. Currently we lack updating the >>> documentation.... this still is work in progress. >>> >>> Jens >>> >>> >>> -----Original Message----- >>> From: Debbie Deuth [mailto:debbiede...@comcast.net] >>> Sent: Mittwoch, 8. Dezember 2010 00:07 >>> To: chemistry-dev@incubator.apache.org >>> Subject: openCMIS 0.2.0-incubating release and query support >>> >>> It appears that there are a number of changes in OpenCMIS 0.2.0 for query >>> support. We are currently implementing a CMIS repository. We have >>> developed >>> RepositoryService, ObjectService, RelationshipService and >>> NavigationService >>> code that makes use of the OpenCMIS 0.1.0 release code. I am currently >>> working on implementing a DiscoveryService query. I was attempting to use >>> a >>> query condition processor extended from AbstractQueryConditionProcessor. >>> I >>> ran into several problems and limitations with this when trying to work >>> with >>> a more complex WHERE clause containing ANDs, ORs and parentheses (e.g., >>> "WHERE (a=1 and b=2) OR (c=4 or d=5)"). It looks like the 0.2.0 code will >>> alleviate many of my problems. >>> >>> >>> >>> Is there any update on when 0.2.0 will be released? Will it be before the >>> end of the year? >>> >>> >>> >>> >>> >>> Debbie Deuth, Prospero Media Services >>> >>> debbiede...@comcast.net >>> >>> >>> >> >> -- >> >> Eng. Gabriele Columbro >> Alfresco Software, Ltd. >> >> >> Blog: http://www.mindthegab.com >> Twitter: http://twitter.com/mindthegabz >> >> >> >> >> > > > > -- > Florent Guillaume, Director of R&D, Nuxeo > Open Source, Java EE based, Enterprise Content Management (ECM) > http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 -- Stefane Fermigier, Founder and Chairman, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com/ - +33 1 40 33 79 87 - http://twitter.com/sfermigier Join the Nuxeo Group on LinkedIn: http://linkedin.com/groups?gid=43314 New Nuxeo release: http://nuxeo.com/dm54 "There's no such thing as can't. You always have a choice."
