Big +1 here. Projects that can't be repeatably built risk decay faster than those that can.
Given the needs of some build chains (especially Windows, in my experience) I also endorse the fact that this does not specifically call out /automated/ builds, though projects should be striving to achieve those as much as possible anyway. -Joan ----- Original Message ----- > From: "Mark Thomas" <ma...@apache.org> > To: dev@community.apache.org > Sent: Wednesday, September 28, 2016 4:33:36 AM > Subject: Addition to the project maturity model > > 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 > build. > > > If there are no objections, I'll add this some time next week. > > Mark > > [1] > https://lists.apache.org/thread.html/cf6a2ea3b969dc0e81ce49650f4418ab2480492c612bd2cacdf070dc@%3Cgeneral.incubator.apache.org%3E > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
