Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-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 D61121021C for ; Tue, 8 Oct 2013 16:55:04 +0000 (UTC) Received: (qmail 52915 invoked by uid 500); 8 Oct 2013 16:55:04 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 52804 invoked by uid 500); 8 Oct 2013 16:55:03 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 52795 invoked by uid 99); 8 Oct 2013 16:55:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 16:55:03 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [74.125.149.18] (HELO na3sys009aog137.obsmtp.com) (74.125.149.18) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Oct 2013 16:54:54 +0000 Received: from mail-qa0-f48.google.com ([209.85.216.48]) (using TLSv1) by na3sys009aob137.postini.com ([74.125.148.12]) with SMTP ID DSNKUlQ4yaPqXeXqMwUBnXpb1aGm71d/Dp+5@postini.com; Tue, 08 Oct 2013 09:54:34 PDT Received: by mail-qa0-f48.google.com with SMTP id hu16so3964419qab.7 for ; Tue, 08 Oct 2013 09:54:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=RZBJB8zJP8NBxGD/kxI5ItpGo8HnQMe80PzBYYV+5gY=; b=GIEVjYssOXuXiUw/4IZg4WPKr+JeEypG8oaMXmTUtAMcOGpqERjS3AuPZ1h2kE4pBp vNw0mYqYllCi3y0QsHwl8I6JcAKuQTpJaxse5G1UHkZWiT6FI4jAzYkNjj6n5SvmT+Qr ObHqR6AYilKmD54TloEc0GZVJ/ETgZhgIIghI5g/ZQc295c58EGyZ5vtspom5Y6aLehs UxN0Qr+2N+9yyXA0O5M1ULxoNrhqReMK6M3yJnJSaHx7Mql1gH76y1l1dLXNgjMK8kIG uxlslwA7g8Svr7MytH79IhUSPb4m3/xn2c5GQiG7AnXDdDpfMS+D8K5sKrRIiep6qT0R zzCw== X-Gm-Message-State: ALoCoQkV5Aoo3ASHdVtj//Xfx9M9AkX5hAeJY5wbAGzHrJxdzVGpcou47IjVSueqCGW8E85b572O7HDGkn/f2BzwZxPcT/Gy+AyrFpLHsG2tqyQIoMLaz8uVRkAa1jFXGvW0Nv6ooJkf7iDTh7fTXbYVU10jvPBxe/RvQnXC5dxFtYqSCO2FpQU= X-Received: by 10.224.130.3 with SMTP id q3mr3129907qas.117.1381251272489; Tue, 08 Oct 2013 09:54:32 -0700 (PDT) X-Received: by 10.224.130.3 with SMTP id q3mr3129884qas.117.1381251272319; Tue, 08 Oct 2013 09:54:32 -0700 (PDT) Received: from localhost ([216.203.6.11]) by mx.google.com with ESMTPSA id g2sm75797349qaf.12.1969.12.31.16.00.00 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 08 Oct 2013 09:54:31 -0700 (PDT) Date: Tue, 8 Oct 2013 12:54:29 -0400 From: Chip Childers To: dev@cloudstack.apache.org Subject: Re: Call for 4.3 and 4.2.1 Release Managers! Message-ID: <20131008165429.GF98582@USLT-205755.sungardas.corp> References: <-1383224870465092932@unknownmsgid> <20131007143332.GH98582@USLT-205755.sungardas.corp> <30e9c045295e43bba999f35c706362dd@WIN-TMPHJ5I2JM4.ANGANI.CO> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Oct 08, 2013 at 04:49:24PM +0000, Animesh Chaturvedi wrote: > > > Whomever wants to take the lead for 4.3 should probably (IMO), start a > > discussion on (1) coordination of work and > [Animesh>] Since we are getting closer to code freeze date and we cannot find overall release management I can pick up 4.3 and call out the roles and ask for volunteers for them. Sounds good. > > (2) re-thinking the schedule > > to reset based on both historic performance and reality of the calendar > > (we've really been working on 4.2 when we should have moved on to 4.3). > [Animesh>] Chip my preference would be to stick to the timeline of 4.3 which will make it a smaller release but will give us the opportunity to clear up our technical debt. +1 to being smaller and tech-debt focused. -chip