Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Received-SPF: pass (nike.apache.org: domain of jhuebel@opentext.com designates
 149.235.128.48 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: TLP releases
Date: Wed, 23 Feb 2011 15:33:10 +0100
Message-ID: <11E8705F4573E64FB42C724ADC742F6F036191C7@MUCXGC2.opentext.net>
In-Reply-To: <4D64F7E8.9080603@alfresco.com>
Thread-Topic: TLP releases
Thread-Index: AcvTUgGvvytR3OFfRiicq6gIQo0ZTAAEngag
References: <4D64F7E8.9080603@alfresco.com>
From: =?iso-8859-1?Q?Jens_H=FCbel?= <jhuebel@opentext.com>
To: <dev@chemistry.apache.org>

I do not see any big issues with going forward with a 0.3.0 TLP release. =
I agree to Gabriele that we need to fix the documentation for 1.0. How =
far is the .Net implementation? Is this something to be ready for a =
release?

For the roadmap a few more points are coming into my mind:
 - Include fulltext query to the parser
 - Rethink project structure for Java (simplification: e.g. do we really =
need 6 different test projects)
 - Rethink our test strategy (why TCK and fit for example? We have =
started a lot but some are not really finished and there is not much =
activity)
 - I would appreciate if we have an examples sub-project for making =
adoption easier and extending the documentation
- need to agree on when/how we want to merge with the CMIS 1.1 branches

Jens


-----Original Message-----
From: Florian M=FCller [mailto:florian.mueller@alfresco.com]=20
Sent: Mittwoch, 23. Februar 2011 13:05
To: dev@chemistry.apache.org
Subject: TLP releases

Hi all,

We are ticking off more and more tasks that are related to the =
graduation.=20
But there is still one big open topic: TLP releases

When do we think can and should we release OpenCMIS and cmislib without =
"incubating" label?

Can we just take the current code and release it? There shouldn't be too =
many changes since the last releases.
Even though the release processes are now slightly different and we have =
to adjust the release packages a bit, it shouldn't take too long to =
prepare the releases.

Opinions?


Cheers,

Florian