Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 77197 invoked from network); 12 Aug 2004 21:00:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 12 Aug 2004 21:00:25 -0000 Received: (qmail 24034 invoked by uid 500); 12 Aug 2004 21:00:19 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 23965 invoked by uid 500); 12 Aug 2004 21:00:19 -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: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 23952 invoked by uid 99); 12 Aug 2004 21:00:19 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received: from [128.195.24.168] (HELO scotch.ics.uci.edu) (128.195.24.168) by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 12 Aug 2004 14:00:16 -0700 Received: from mvata-64-75.cruznet.ucsc.edu (scotch.ics.uci.edu [128.195.24.168]) (authenticated bits=0) by scotch.ics.uci.edu (8.12.6/8.12.6) with ESMTP id i7CL0B2q014857 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 12 Aug 2004 14:00:12 -0700 (PDT) Date: Thu, 12 Aug 2004 14:00:11 -0700 From: Justin Erenkrantz To: dev@httpd.apache.org, jim@jaguNET.com Subject: Re: httpd-2.2 release roadmap v0.1 Message-ID: <318C8D6C5D9B8C678B9F0716@mvata-64-75.cruznet.ucsc.edu> In-Reply-To: References: <200408122015.i7CKFX323585@devsys.jaguNET.com> X-Mailer: Mulberry/3.1.5 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, score=-0.1 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.0-pre1-r21475 X-Spam-Checker-Version: SpamAssassin 3.0.0-pre1-r21475 (2004-06-19) on scotch.ics.uci.edu X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --On Thursday, August 12, 2004 4:20 PM -0400 Joshua Slive wrote: > I would hope we could make a statement like: "Major security issues will be > addressed in 2.0 until at least [2.2 release date + 1 year]." If someone volunteers to be a 2.0 security RM, that'll happen. Otherwise, it won't. ;-) -- justin