Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
MIME-Version: 1.0
In-Reply-To: <30083931.967.1475087318946.JavaMail.Joan@RITA>
References: <10d3a222-0bd0-c232-69b1-fd678ca21df6@apache.org> <30083931.967.1475087318946.JavaMail.Joan@RITA>
From: Stian Soiland-Reyes <stain@apache.org>
Date: Thu, 29 Sep 2016 14:09:01 +0100
Message-ID: <CAMBJEmUhnWC5+EYvg7tnjfCK+Qj1mC4FA3V-fpbG86TNSCcs2g@mail.gmail.com>
Subject: Re: Addition to the project maturity model
To: dev@community.apache.org
Content-Type: text/plain; charset=UTF-8
archived-at: Thu, 29 Sep 2016 13:09:25 -0000

On 28 September 2016 at 19:26, Joan Touzet <joant@lrtw.org> wrote:
> Big +1 here. Projects that can't be repeatably built risk decay
> faster than those that can.

+1 - as long as it is documented it doesn't matter if it says "copy
the file three times while jumping high in the air".

Obviously automated build/release simplifies things - documentation
would also highlight any special build infrastructure.


Not sure how a project can prove the "someone new to the project" bit
- perhaps this can be motivation to encourage new committers to (try
to) do a release?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org