I agree to this proposal. Makes sense. Perhaps everyone should have look at the new page and check the current scoping of the project names. If there is any objection it would be better to discuss this now... With the official CMIS release I expect some more visibility of this project.
Jens -----Original Message----- From: Goetz, Paul [mailto:[email protected]] Sent: Montag, 10. Mai 2010 17:33 To: [email protected] Subject: RE: OpenCMIS release proposal Hi, concerning the release documentation: In order to be able to separate the documentation for the different topics (cmislib, Internal, OpenCMIS), I would propose that we do this via child pages. This means that the documentation for a specific topic has to be a child document of that topic (e.g. all documentation for OpenCMIS has to be child to "OpenCMIS"). If this is ok for everyone, then this has to be kept in mind when adding new pages... Best regards, Paul -----Original Message----- From: Florian Müller [mailto:[email protected]] Sent: Montag, 10. Mai 2010 16:34 To: [email protected] Subject: OpenCMIS release proposal Hi all, Here is a proposal how an OpenCMIS release could look like: [1] The script that generates these files is in the OpenCMIS SVN branch in the release-tools directory. It does not create branches and tags in SVN yet. It only produces the release packages. The main release package is the source package ([2]/[3]). Only this packages contains the documentation. All other packages are just convenience packages with binaries. I'm currently compiling a release documentation. A first draft is already in the Wiki but I need a few more days to finish it. WDYT? Cheers, Florian [1] http://people.apache.org/~fmui/opencmis/ [2] http://people.apache.org/~fmui/opencmis/chemistry-opencmis-0.1-incubating-RC0.1-source.zip [3] http://people.apache.org/~fmui/opencmis/chemistry-opencmis-0.1-incubating-RC0.1-source.tar.gz
