Phil Steitz wrote: > On 4/30/13 10:29 AM, sebb wrote: >> On 30 April 2013 18:25, Phil Steitz <[email protected]> wrote: >> >>> On 4/30/13 10:19 AM, sebb wrote: >>>> On 30 April 2013 17:52, Phil Steitz <[email protected]> wrote: >>>> >>>>> On 4/30/13 9:28 AM, sebb wrote: >>>>>> On 30 April 2013 16:59, Honton, Charles <[email protected]> >>>>> wrote: >>>>>>> Is there any policy concern with publishing the binaries of alpha >>>>>>> releases, after vote, to a Apache snapshot repository which is not >>>>>>> replicated to Maven Central? >>>>>>> >>>>>>> >>>>>> Not sure that question makes sense as posed. >>>>>> >>>>>> If a build is voted on, it is a release, and is not a snapshot. >>>>>> AFAIK snapshots are never voted on so cannot become releases. >>>>>> >>>>>> Snapshots can be uploaded to a snaphot repo without needing a vote. >>>>>> >>>>>> Snapshots can (*) only be uploaded to snapshot repos; they cannot be >>>>>> uploaded to release repos. >>>>>> AFAIK the reverse is also true, releases are never uploaded to >>>>>> snapshot repos. >>>>> IIRC, what we did with the [lang] 3.0 betas was not push the beta >>>>> releases to maven central, but we *did* update the snapshot repos. >>>>> >>>> I'm not sure it's possible to upload a non-SNAPSHOT bundle to the >>> snapshots >>>> repo via Nexus, but I could be wrong. >>> It was labelled 3.0-SNAPSHOT, IIRC. >>> >>> >> But surely that's not an Alpha or a Beta release? > > The actual release is what is on the ASF mirrors. Pointing people > at the SNAPSHOT for maven-assisted testing was a workaround. Seems > a reasonable workaround to me. The problem with the public maven > repos is you can never delete anything from them and we don't want > the betas to be long-lived in the wild.
+1 - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
