Re: Addition to the project maturity model

2016-10-25 Thread Mark Thomas
On 04/10/2016 09:11, Bertrand Delacretaz wrote: > On Tue, Oct 4, 2016 at 9:50 AM, Mark Thomas wrote: >> ...I'm wondering about expanding "... generate a release." to "... generate >> the complete set of artifacts required for a release." > > Works for me, it's more precise. Done. Mark ---

Re: Addition to the project maturity model

2016-10-04 Thread Bertrand Delacretaz
On Tue, Oct 4, 2016 at 9:50 AM, Mark Thomas wrote: > ...I'm wondering about expanding "... generate a release." to "... generate > the complete set of artifacts required for a release." Works for me, it's more precise. -Bertrand --

Re: Addition to the project maturity model

2016-10-04 Thread Mark Thomas
On 04/10/2016 08:22, Bertrand Delacretaz wrote: > Hi, > > On Wed, Sep 28, 2016 at 10:33 AM, Mark Thomas wrote: >> I'd like to propose the following addition to the project maturity model. >> >> RE50 >> The release process is documented and repeatable to

Re: Addition to the project maturity model

2016-10-04 Thread Bertrand Delacretaz
Hi, On Wed, Sep 28, 2016 at 10:33 AM, Mark Thomas wrote: > I'd like to propose the following addition to the project maturity model. > > RE50 > The release process is documented and repeatable to the extent that > someone new to the project is able to independently genera

Re: Addition to the project maturity model

2016-10-01 Thread Phil Steitz
On 9/29/16 6:25 AM, William A Rowe Jr wrote: > On Wed, Sep 28, 2016 at 3:33 AM, Mark Thomas wrote: > >> All, >> >> After a discussion on the general@incubator.a.o mailing list [1], I'd >> like to propose the following addition to the project maturity model. &

Re: Addition to the project maturity model

2016-09-30 Thread Bertrand Delacretaz
On Thu, Sep 29, 2016 at 3:44 PM, Stian Soiland-Reyes wrote: > ...I'm not sure what is the deal with the BASIC line numbering idea of > RE* - Hehe, that idea came from someone who has actually been doing BASIC in the past...on a Sharp calculator that was passed around during boring classes in

Re: Addition to the project maturity model

2016-09-29 Thread Stian Soiland-Reyes
ng list [1], I'd >> like to propose the following addition to the project maturity model. >> >> RE50 >> The release process is documented and repeatable to the extent that >> someone new to the project is able to independently generate a release >> build. >> &

Re: Addition to the project maturity model

2016-09-29 Thread William A Rowe Jr
On Wed, Sep 28, 2016 at 3:33 AM, Mark Thomas wrote: > All, > > After a discussion on the general@incubator.a.o mailing list [1], I'd > like to propose the following addition to the project maturity model. > > RE50 > The release process is documented and repeatable to

Re: Addition to the project maturity model

2016-09-29 Thread Stian Soiland-Reyes
On 28 September 2016 at 19:26, Joan Touzet 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/rel

Re: Addition to the project maturity model

2016-09-28 Thread Joan Touzet
ng to achieve those as much as possible anyway. -Joan - Original Message - > From: "Mark Thomas" > To: dev@community.apache.org > Sent: Wednesday, September 28, 2016 4:33:36 AM > Subject: Addition to the project maturity model > > All, > > After a discussi

Re: Addition to the project maturity model

2016-09-28 Thread Niclas Hedhman
bator.a.o mailing list [1], I'd > like to propose the following addition to the project maturity model. > > RE50 > The release process is documented and repeatable to the extent that > someone new to the project is able to independently generate a release > build. > >

Addition to the project maturity model

2016-09-28 Thread Mark Thomas
All, After a discussion on the general@incubator.a.o mailing list [1], I'd like to propose the following addition to the project maturity model. RE50 The release process is documented and repeatable to the extent that someone new to the project is able to independently generate a release