Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 93648 invoked from network); 10 Sep 2005 00:28:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Sep 2005 00:28:11 -0000 Received: (qmail 5244 invoked by uid 500); 10 Sep 2005 00:28:08 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 5220 invoked by uid 500); 10 Sep 2005 00:28:08 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 5207 invoked by uid 99); 10 Sep 2005 00:28:08 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2005 17:28:08 -0700 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_40_50,HTML_MESSAGE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of mfncooper@gmail.com designates 64.233.184.202 as permitted sender) Received: from [64.233.184.202] (HELO wproxy.gmail.com) (64.233.184.202) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2005 17:28:20 -0700 Received: by wproxy.gmail.com with SMTP id i13so1754503wra for ; Fri, 09 Sep 2005 17:28:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=GxibeT9K7TUVSktK/G12fKIT3xE33arjqmPnSSLBJ+AUKUOWiRIi+YOcSJqvoF6AwD7vrZ0wgvFVldvUk7p4mz+f8IZKnW+t85p9X6KdQ9ZtOK2M0J7TRaz0qX3n46PdAEo5WGhfkpzQbQq6Exq5rcgIhDM2mrThnfNoGIQnG3U= Received: by 10.54.129.15 with SMTP id b15mr302044wrd; Fri, 09 Sep 2005 17:28:06 -0700 (PDT) Received: by 10.54.57.63 with HTTP; Fri, 9 Sep 2005 17:28:06 -0700 (PDT) Message-ID: <16d6c6200509091728b07bfa8@mail.gmail.com> Date: Fri, 9 Sep 2005 17:28:06 -0700 From: Martin Cooper Reply-To: mfncooper@gmail.com To: Jakarta Commons Developers List , donald.brown@gmail.com Subject: Re: [validator] Release preparation In-Reply-To: <1c661f2f050909171346d96b27@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1972_11650248.1126312086450" References: <1c661f2f050909171346d96b27@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_1972_11650248.1126312086450 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 9/9/05, Don Brown wrote: >=20 > Ok, I think Commons Validator is ready for a release. All the bugs are > closed, the site build issue has been resolved, and the javadocs for the > Javascript files are building correctly. Should this next release be a=20 > beta > or release canidate? Do I need to obtain some sort of key to sign the=20 > jars? Beta versus RC depends on the scale of the changes since the last release, = I=20 think. In general, I'd prefer to see a Beta first, but I would't -1 an RC i= f=20 the changes are not dramatic. As for signing jars, we haven't been doing that. We do sign the downloads,= =20 though (meaning the .zip and .tar.tz files). -- Martin Cooper TIA, >=20 > Don >=20 > ------=_Part_1972_11650248.1126312086450--