Return-Path: X-Original-To: apmail-openjpa-dev-archive@www.apache.org Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5E2194E2 for ; Sat, 4 Feb 2012 16:42:53 +0000 (UTC) Received: (qmail 87348 invoked by uid 500); 4 Feb 2012 16:42:53 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 87185 invoked by uid 500); 4 Feb 2012 16:42:52 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 87177 invoked by uid 99); 4 Feb 2012 16:42:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Feb 2012 16:42:51 +0000 X-ASF-Spam-Status: No, hits=3.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of allee8285@gmail.com designates 209.85.217.174 as permitted sender) Received: from [209.85.217.174] (HELO mail-lpp01m020-f174.google.com) (209.85.217.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Feb 2012 16:42:45 +0000 Received: by lbom4 with SMTP id m4so989633lbo.33 for ; Sat, 04 Feb 2012 08:42:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=owiGLjMYhzQZyhudnbBDtM9Y1OkgOH6Vhc8eYaEJTrI=; b=v2t5BUTiSIjkcpuSrTKvu1LzsHuB+lGHhTCH3GKLQByPQRmGKhGlQzMnX/e1mu/a12 JkeOWVc6JHap+n19q8swETUFA8bIMrhNCjPoU+xXMwXZ7tMSYaPjHjL7kWSs04IiLk8g 68r5PNo1SE3gHhFtVJfeWi8YgOsChM2RBwoRk= MIME-Version: 1.0 Received: by 10.112.27.162 with SMTP id u2mr2954778lbg.70.1328373743379; Sat, 04 Feb 2012 08:42:23 -0800 (PST) Received: by 10.112.5.134 with HTTP; Sat, 4 Feb 2012 08:42:23 -0800 (PST) In-Reply-To: <1328318587387-7252909.post@n2.nabble.com> References: <1328318587387-7252909.post@n2.nabble.com> Date: Sat, 4 Feb 2012 10:42:23 -0600 Message-ID: Subject: Re: OpenJPA 2.2.0 release plan From: Albert Lee To: dev@openjpa.apache.org Content-Type: multipart/alternative; boundary=bcaec555565c1a675404b8261d4b X-Virus-Checked: Checked by ClamAV on apache.org --bcaec555565c1a675404b8261d4b Content-Type: text/plain; charset=ISO-8859-1 Until we formalize the new recommendation, I am going to stick with the current 3 working days proposal unless we hear other objections or special need from the community. Monday or Friday release is as good as any other day of the week. Monday actually gives the community a couple week-end days to react to the proposal. Any choice would be an arbitrary choice and can be argued one way or the other. On Fri, Feb 3, 2012 at 7:23 PM, Pinaki Poddar wrote: > Hi Albert, > > Please post your concerns, comments or suggestions (if any) to this dev > > mailing list. > We should formalize that a notice for branching and code freeze on trunk > must be at least of seven calendar days or five working days in advance. I > have mentioned that before when Mark planned for a 2.2.0 branch. > > This is to give the community members a scope to discuss and complete their > ongoing work. > > > We plan to copy trunk to 2.2.x branch on 2/6/2012 (Mon) > Also a middle of the week is a better choice for a code freeze than Monday > or Friday. Not only in this case, but in general. > > ----- > Pinaki Poddar > Chair, Apache OpenJPA Project > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/OpenJPA-2-2-0-release-plan-tp7248474p7252909.html > Sent from the OpenJPA Developers mailing list archive at Nabble.com. > -- Albert Lee. --bcaec555565c1a675404b8261d4b--