Looking at this thread: http://www.nabble.com/-VOTE--approve-the-m1-release-of-Trinidad%27s-Maven-plugins-tf2180114.html
It looks the trinidad just went through something similar and they just did a mvn deploy and then voted on the binaries. On 9/7/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
Dear Mentors, I've got tag of the code that should become the 4.1-incubator release of the activemq maven plugins. It's located here: https://svn.apache.org/repos/asf/incubator/activemq/maven-plugins/tags/maven-plugins-4.1/ Now.. I started following the normal release procedure that I normally take for activemq, but I realized that it might not be such a good idea. This is mainly because maven plugins depend on some special deployment updating of the maven-metadata xml in the deployment repository. And this special updating normally happens when mvn deploy is running. So while I could provide you a binary build for you guys to inspect, once it's approved, I would need to re-run the build to do the mvn deploy bits. So, can we just call a vote to do a build and release what is located the the tag listed above? I believe the the maven project follow a similar release procedure but I'm not sure if the incubator pmc would approve of it. On 9/7/06, Hiram Chirino <[EMAIL PROTECTED]> wrote: > Hey folks.. now that the repo reorg is done.. we can do a release of > the maven plugins that our main activemq build depends on without > having to release everything. > > So... I'm going to start working on cutting a release of the stuff > under https://svn.apache.org/repos/asf/incubator/activemq/maven-plugins/trunk > > Let me know if I should hold off. Since they have been working well > now for while, I'm assuming they are stable enough for a release. > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > -- Regards, Hiram Blog: http://hiramchirino.com
-- Regards, Hiram Blog: http://hiramchirino.com
