> -----Original Message----- > From: Mark Struberg [mailto:strub...@yahoo.de.INVALID] > Sent: Friday, August 19, 2016 03:19 > To: general@incubator.apache.org > Subject: Re: Ease of release process and exit criteria > > Good links. > > I’d like to add some information for projects who use GIT with maven: [ ... ] > Note that in most projects we do _not_ push the release candidate > directly to the ASF repo but e.g. to the release managers private github > account. > Reason is that we cannot easily get rid of it from the cannonical ASF > repo if the VOTE fails. > (ASF repos get mirrored downstream in seconds, and while we could > technically remove it from our own repo we have no control over all the > clones). [orcmid]
The ASF SVN supports a staging process by which projects have a place to put dev-only builds that are for testing and consideration as release candidates. How that would tie into GIT-only projects and Maven as used is a different matter and distinguishing between non-released developer artifacts, release candidates, and releases seems to be much trickier. Using AOO as an example, the place where artifacts for dev-only use and handling as release candidates are at <https://dist.apache.org/repos/dist/dev/openoffice>. Release candidates on which deliberation fails to achieve release approval can be deleted from there. When a release candidate is identified and approved as a release, it is copied or moved to <https://dist.apache.org/repos/dist/release/openoffice> along with the signatures and hashes that were with the candidate in the dev area. (Using SVN, this is a cheap copy.) That is the staging point for a general, public distribution. Within something like 24-48 hours, the content of that release area is automatically mirrored to <https://archive.apache.org/dist/openoffice> And THAT is the official public availability point (with whatever mirroring and other downstream distribution there happens to be). That is where the indelible KEYS, hashes, signatures, etc. are to be accessed and the material is preserved in perpetuity. Deletions at dist.apache.org do not have any effect on the archive.apache.org artifacts, so one can clean-up by removing those. This is SVN so the artifacts are not completely gone, but they are not available for mistaken download by direct access to those locations. > > This is kind of symetrical to the maven repo staging aproach. > And the sha1 is the same anyway if we merge the buid-branch to master > and push it to the ASF repo later (when the VOTE did pass). > > Something very old I wrote up for DeltaSpike a few years ago where I > described the steps: > http://mail-archives.apache.org/mod_mbox/deltaspike- > dev/201309.mbox/%3c1378906506.82251.yahoomail...@web28902.mail.ir2.yahoo > .com%3E > > hth. > > LieGrue, > strub > > > > Am 19.08.2016 um 11:57 schrieb Bertrand Delacretaz > <bdelacre...@apache.org>: > > > > Hi Mark, > > > > On Fri, Aug 19, 2016 at 11:23 AM, Mark Thomas <ma...@apache.org> > wrote: > >> ...I'm thinking of a graduation criteria long the lines of: > >> "Is the release process clearly documented to the point that someone > new > >> to the project could produce a release build?"... > > > > I like this - as another example we have > > http://sling.apache.org/documentation/development/release- > management.html > > in Sling, and as someone who does releases in bursts that's very > > useful. > > > >> ...If there is general consensus on this, I'm happy to draft > something to > >> add to http://incubator.apache.org/guides/graduation.html#releases > ... > > > > +1 and it's good to add links such as the ones you mentioned and the > > above if you think they are good examples. > > > > How about also adding an RE50 item to > > https://community.apache.org/apache-way/apache-project-maturity- > model.html > > about a repeatable release process? That's a discussion for > > community.a.o but what's your opinion? > > > > -Bertrand > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
