Hey guys, I'm up for a weekend 0.4.0 release, most likely Sunday will give me time since Italian football championship is finally done :)
I will add the JCR bridge to the release packages and also (tentatively) try to set up a procedure for automatic deployment upon release of Javadocs to the Apache CMS (could do with maven wagon-webdav). I'd then suggest to commit any leftover before Sat! HTH, Gab On May 25, 2011, at 8:08 PM, Klevenz, Stephan wrote: > Hi, > > I would like to come back to Florians roadmap proposal to trigger a new 0.4.0 > release. Time is mature, a lot of bugfixes were done, Apache Retreat is > behind us, CMIS F2F takes place right now and CMIS 1.1 comes to front. > > Is there anything that hinders us from having a new release? > > Here is a sorted JIRA filter on open issues. > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?sorter/field=fixVersions&sorter/order=ASC > > CMIS-240 is only a wish. > CMIS-369 will close soon after testing. > > I also would like to ask Gab if you can support in release operation? > > WDYT? > > Regards, > Stephan > > >> Hi all, >> >> I would like to propose an OpenCMIS roadmap: >> >> - Release 0.x.0 versions every 2-3 months, regardless of what we have done, >> and release 0.4.0 >> immediately. >> - Complete the Browser Binding (CMIS 1.0 scope, client and server) and the >> JCR Bridge and >> then release 1.0.0. (Late summer?) >> - In parallel, start OpenCMIS 2.x in a new branch when the CMIS 1.1 draft is >> stable enough >> to be implemented. (In a few months?) >> OpenCMIS 2.x should support CMIS 1.0 and CMIS 1.1 >> >> What do you think? >> >> >> Florian >
