Brian, can you point me to any thread of that discussion? I'm not going to pick up the conversational gambit of what the policy *should* be; I'm already neck deep in that on another thread and I don't think it will help anyone to start a mirror image of it here.
On Fri, Dec 21, 2012 at 1:19 PM, Brian Fox <bri...@infinity.nu> wrote: > Further to that, no one will ever consume maven plugins from a random dist > folder anyway, so a policy that requires this is a paper policy only and > would have no basis in the reality of how these particular projects are > consumed. > > > On Fri, Dec 21, 2012 at 1:18 PM, Brian Fox <bri...@infinity.nu> wrote: > >> The last discussion of this required the production of proper source >> bundles for voting, which we created at that time. I don't recall there >> being any requirement that everything go onto dist. >> >> >> On Fri, Dec 21, 2012 at 10:57 AM, Benson Margulies >> <bimargul...@gmail.com>wrote: >> >>> Dear fellow community members, >>> >>> The current official documentation for Apache releases calls for all >>> releases to be copied to the 'dist' area. >>> >>> We don't do that for poms and plugins. We just push a source release >>> zip to repository.apache.org. >>> >>> Can anyone here help me out by finding a historical thread of >>> discussion that approved this plan of attack? >>> >>> I'm setting out to edit the official page to memorialize this policy >>> for the benefit of other projects, and I'm getting pushback. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
