That is an interesting one. And funny enough, there are two parts of that IMHO.
1. Check out from source control repository, and re-produce a source release build, resulting in a releasable artifact. 2. That the built artifact can be downloaded, and built for a given platform/deployment. In my project, we actually have the CI do the second step, verifying that the release source artifact can be built on its own from tar file. I have not seen that very often... Cheers Niclas On Wed, Sep 28, 2016 at 4:33 PM, Mark Thomas <ma...@apache.org> 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 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/cf6a2ea3b969dc0e81ce49650f4418 > ab2480492c612bd2cacdf070dc@%3Cgeneral.incubator.apache.org%3E > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
