-0 I don't think this sort of things belongs in Commons proper as a component. What we advertise, release and support from commons proper are general purpose libraries that developers can use in their own applications. This is what Commons was created for. While the staging plugin looks like a useful thing for internal commons use, I don't see it as a general purpose component. I see it like the download plugin or commons parent. Perhaps what we should do is formalize our policy to allow release of internal tools so they can be grabbed from maven repos without actually promoting them on the main commons web page or committing to support them for external use.
Phil On 6/21/13 7:06 AM, sebb wrote: > [I'm not sure a vote for this is really needed, but] > > I'd like to move the staging plugin from the sandbox to commons > proper, so it can be released for use by Commons. > > The component name is currently > > commons-staging-plugin > > I propose to keep the same name unless there are objections. > > The vote will close no sooner than 72 hours from now. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
