Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 63187 invoked from network); 3 Apr 2006 13:30:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Apr 2006 13:30:41 -0000 Received: (qmail 46370 invoked by uid 500); 3 Apr 2006 13:30:39 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 46006 invoked by uid 500); 3 Apr 2006 13:30:38 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 45993 invoked by uid 99); 3 Apr 2006 13:30:38 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Apr 2006 06:30:38 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ralph.goers@dslextreme.com designates 66.51.199.81 as permitted sender) Received: from [66.51.199.81] (HELO mail5.dslextreme.com) (66.51.199.81) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 03 Apr 2006 06:30:37 -0700 Received: (qmail 25248 invoked from network); 3 Apr 2006 13:29:39 -0000 Received: from unknown (HELO [127.0.0.1]) (66.51.196.164) by mail5.dslextreme.com with SMTP; Mon, 03 Apr 2006 06:29:39 -0700 Message-ID: <44312377.1010006@dslextreme.com> Date: Mon, 03 Apr 2006 06:30:31 -0700 From: Ralph Goers Reply-To: rgoers@apache.org User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [IMP] Code freeze for 2.1.x References: <442CF109.9010801@apache.org> <20060403102725.GA1591@vision.anyware> In-Reply-To: <20060403102725.GA1591@vision.anyware> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N In case you didn't know, the code freeze doesn't mean you can't check in. It means you can only fix bugs - preferably those found during testing of the potential release. So yes, because trunk and the branch are shared then these rules apply to it as well. Ralph Jean-Baptiste Quenot wrote: > * Carsten Ziegeler: > > >> As voted recently the code freeze for 2.1.9 starts *now* and >> hopefully ends with the release in one week. >> > > I've got a question: does this code freeze also affect trunk? I > just made a slight modification in CForms, and realized that as we > have the same sources for trunk and 2.1, I might have violated the > rule... > > Shall I be blamed for that? >