Return-Path: X-Original-To: apmail-httpd-dev-archive@www.apache.org Delivered-To: apmail-httpd-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 53A12CCAD for ; Thu, 11 Jul 2013 12:00:01 +0000 (UTC) Received: (qmail 81851 invoked by uid 500); 11 Jul 2013 11:59:55 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 81802 invoked by uid 500); 11 Jul 2013 11:59:55 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 81779 invoked by uid 99); 11 Jul 2013 11:59:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jul 2013 11:59:54 +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 (athena.apache.org: local policy) Received: from [195.232.224.70] (HELO mailout01.vodafone.com) (195.232.224.70) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jul 2013 11:59:47 +0000 Received: from mailint01.vodafone.com (localhost [127.0.0.1]) by mailout01.vodafone.com (Postfix) with ESMTP id 193F22E1DF1 for ; Thu, 11 Jul 2013 13:59:25 +0200 (CEST) Received: from VOEXC03W.internal.vodafone.com (voexc03w.dc-ratingen.de [145.230.101.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint01.vodafone.com (Postfix) with ESMTPS id 074992E1DCF for ; Thu, 11 Jul 2013 13:59:25 +0200 (CEST) Received: from VOEXC08W.internal.vodafone.com (145.230.101.28) by VOEXC03W.internal.vodafone.com (145.230.101.23) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 11 Jul 2013 13:59:24 +0200 Received: from VOEXM09W.internal.vodafone.com ([169.254.1.136]) by voexc08w.internal.vodafone.com ([145.230.101.28]) with mapi id 14.02.0328.011; Thu, 11 Jul 2013 13:59:24 +0200 From: =?iso-8859-1?Q?Pl=FCm=2C_R=FCdiger=2C_Vodafone_Group?= To: "dev@httpd.apache.org" Subject: RE: [VOTE] The 'RM' Baton Thread-Topic: [VOTE] The 'RM' Baton Thread-Index: AQHOfTiaCAGe/rtql0SpWXyB+RRbFpldsdeAgAATIgCAAJk2AIAA35YAgAAj2wA= Date: Thu, 11 Jul 2013 11:59:22 +0000 Message-ID: References: <20130710014107.38de654a@hub> <8253AC22-B52B-425E-A552-1B631014EA98@jaguNET.com> <51DDE084.3020505@apache.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org > -----Original Message----- > From: Jim Jagielski=20 > Sent: Donnerstag, 11. Juli 2013 13:51 > To: dev@httpd.apache.org > Subject: Re: [VOTE] The 'RM' Baton >=20 >=20 > On Jul 10, 2013, at 6:30 PM, Guenter Knauf wrote: > > > > also I would be +++1 for making fix dates for releases, f.e. lets say > 4 times a year which means all 3 months - and then doing the release > *REGARDLESS* if we have thing hanging in STATUS or not! What doesnt go > into this release does make it for the next, and that would then only be > 3 months. > > But I would *NOT* vote for such unless I'm self able to do releases. > > >=20 > One of the great things about FOSS and esp about this project is > that we've resisted being driven by schedules. We've always had > the mentality that we release when we're ready and don't have > artificial timetables driving releases. +1 Regards R=FCdiger