Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 61939 invoked from network); 28 Mar 2010 14:49:47 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Mar 2010 14:49:47 -0000 Received: (qmail 50854 invoked by uid 500); 28 Mar 2010 14:49:46 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 50728 invoked by uid 500); 28 Mar 2010 14:49:46 -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 50720 invoked by uid 99); 28 Mar 2010 14:49:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Mar 2010 14:49:46 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=AWL,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates 209.85.220.210 as permitted sender) Received: from [209.85.220.210] (HELO mail-fx0-f210.google.com) (209.85.220.210) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Mar 2010 14:49:41 +0000 Received: by fxm2 with SMTP id 2so753309fxm.10 for ; Sun, 28 Mar 2010 07:49:19 -0700 (PDT) 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:received:message-id:subject:from:to:content-type; bh=RDI2bk3IMSAVrINs6EYLKJlmWNCkkI9feEU6z2IrD20=; b=nIEfGsYM7zls1S1zeUS+Z9+6p8mWdUceZ28niDBXzfrFG2BSDrEGf9FHOZf1vUCcFF 9g2pa/lFcdST5FSBRBLhJnT2wvTuouuc9bKV0F+xtAqS9yoAopHbxzxvLupGRty8glNm 5fhv5lEkuTUCle0eQF0O3azcPu3vSkuuGKB60= 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; b=vfMtD+EZvqH0/f9MWttCf5UYKavqeILHNdAkt+82D2gmJ0fpggyE2wfDULC5xUnMyq C+1qcJ/IW5zZb9zpTIPyB3cVcNOBoEaSktbz6V2iGsJz3gGb3QjkNG6Cq0hdztA7tH96 zp+o6twkc753RVrpNMQWYOwYFvn8K7iuXTIGA= MIME-Version: 1.0 Received: by 10.239.188.13 with HTTP; Sun, 28 Mar 2010 07:49:19 -0700 (PDT) In-Reply-To: <1269787365920-1694143.post@n4.nabble.com> References: <1269787365920-1694143.post@n4.nabble.com> Date: Sun, 28 Mar 2010 15:49:19 +0100 Received: by 10.239.193.4 with SMTP id g4mr317023hbi.192.1269787759685; Sun, 28 Mar 2010 07:49:19 -0700 (PDT) Message-ID: <25aac9fc1003280749s2d6aed5bua4564d87c809ccd7@mail.gmail.com> Subject: Re: Is the release process for micro/hotfix releases the same as major ones? From: sebb To: Commons Developers List Content-Type: text/plain; charset=ISO-8859-1 On 28/03/2010, henrib wrote: > > I'm considering releasing JEXL-2.0.1 which corrects 2 bugs; do I have to > publish an RC and call vote or is there any expedite process that can be > used? I would say yes, always create an RC for any official release. > Sorry if this is a silly question. > Regards, > Henrib > > > -- > View this message in context: http://n4.nabble.com/Is-the-release-process-for-micro-hotfix-releases-the-same-as-major-ones-tp1694143p1694143.html > Sent from the Commons - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org