Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAPaJBx4cf-r1Dk0n1xn+f+9L8LH37Ky49DEyroe2wt1-o_+Fxg@mail.gmail.com>
References: 
 <CAPaJBx4cf-r1Dk0n1xn+f+9L8LH37Ky49DEyroe2wt1-o_+Fxg@mail.gmail.com>
Date: Tue, 26 Mar 2013 18:14:55 -0700
Message-ID: 
 <CAAS6=7jERqWSmOATar-DT1HEWSbcrnSJzg1vxRUeLEk5LS0Q3Q@mail.gmail.com>
Subject: Re: Creating announce@ lists by default
From: Marvin Humphrey <marvin@rectangular.com>
To: general@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 26, 2013 at 4:05 AM, Noah Slater <nslater@apache.org> wrote:

> I am under the impression that having a low-volume, high-signal
> announcement channel is generally beneficial to most projects that try it.

I agree that such lists are useful.  I like to subscribe to individual
announce lists for security purposes because aggregate lists like
debian-security-announce generally lag behind upstream.  Individual dev lists
and announce@a.o are too high traffic and programming text-based filters is
tricky because conventions like "ANNOUNCE" are not adhered to 100% of the
time.

As to whether such lists should be encouraged for new podlings (probably by
putting a stub in the proposal template alongside the other lists), I can't
say that I have a strong opinion.

Marvin Humphrey

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org