On Wed, Aug 17, 2011 at 2:54 PM, Brett Porter <[email protected]> wrote: > > On 18/08/2011, at 2:39 AM, Benson Margulies wrote: > >> Unless we made use of a 'mirror trick'? I'm not sure that the >> following hangs together. What if there was a repo group for us at >> repository.apache.org that aggregated the staging repos for a flock of >> pom changes, and maven developers knew where to find a settings.xml >> with a mirror-of-* (to avoid adding <repository> elements to poms) >> that searched it in place of central? Then a releaser of the flock >> could stage the first, commit to it, stage the second ..., and then >> call a vote. (Except that this would require 'open' staging repos to >> be visible, which I fear that they are not?) > > That's what I was going to suggest in response to Hervé's last message. > Instead of bumping to a new snapshot immediately, it'd be better if the CI > system could see the staging repositories (assuming the local repos are > periodically cleaned so any failed releases don't stick around).
+1 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
