Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 13743 invoked from network); 28 Feb 2009 11:44:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Feb 2009 11:44:37 -0000 Received: (qmail 38467 invoked by uid 500); 28 Feb 2009 11:44:35 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 38381 invoked by uid 500); 28 Feb 2009 11:44:34 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 38370 invoked by uid 99); 28 Feb 2009 11:44:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Feb 2009 03:44:33 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of grobmeier@gmail.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-fx0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Feb 2009 11:44:26 +0000 Received: by fxm20 with SMTP id 20so1408976fxm.42 for ; Sat, 28 Feb 2009 03:44:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=6rkNrebL1FC/gnGnt6TDiPS3Y3QPOf4j/Rd4gPGyTcA=; b=XkVDI4H7KkvpuNa9MW/oWV29SIWcISdV7uBYrQmAT9yLf2XWKbOk3uEWaXF7v7xB+z 3TFK/T/vS9zdWIHnH/Mnnbt3LOJVfWA6HwQwSpgAOlBgC02przrYnGjyBf8HwztRijDF rnUFXCJLa60s84UmCva303yr2xwLfURVe/UPo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=XXzQ6dcie1j0NdF0M3KU0xwjfzrsYac4QPZ/T5EFGDl7XD8m7aOiZyIzkrAda3IyHD H5fSnME2DvCy1/3N9rP4/VNEalX3MI82qXrviVNFTZoZ33niv5yfZ/tpehaUWCv4Rseg BAcTTPacbfApiNQHi3EPNQixFFpcaoNnvuIO0= MIME-Version: 1.0 Received: by 10.223.114.79 with SMTP id d15mr4183128faq.88.1235821445565; Sat, 28 Feb 2009 03:44:05 -0800 (PST) In-Reply-To: <25aac9fc0902271031m4f2177cey757f178454135ad0@mail.gmail.com> References: <510143ac0902260620v33d50c38oda9c36ffc5c02142@mail.gmail.com> <6c59d89a0902260843o55c52df1q247c6994da28bd14@mail.gmail.com> <25aac9fc0902271031m4f2177cey757f178454135ad0@mail.gmail.com> Date: Sat, 28 Feb 2009 12:44:05 +0100 Message-ID: Subject: Re: [compress] Schedule for a release? From: Christian Grobmeier To: Commons Developers List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org >> =C2=A0In parallel to "graduation" we may be able to finish the stuff we = want >> =C2=A0to see done before the 1.0 release. > > I'd like to see some statements in the Javadoc about the intended > thread safety or otherwise of the classes. > However, if there are any classes that are thread-hostile (*), (I've > not noticed any) I would expect these to be fixed before release! Additionally we have to: - improve maven site stuff, which is a bit outdated now - check Ar-Implementation (see my other mail today) - check CPIO implementation a bit better, since its very new at compress There are several new issue on jira - 7 majors, 1 blocker. Looking at all todos I am guessing that ChangeSet implementation could be finished in time before a release. :-) What about end of march with a possible release date? Would this be possible? I could improve the testcases, the change set implementation and the site stuff (well, which would need a review of english grammar then). Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org