Nice idea, but push it to central to test the whole chain. G
On Thu, Oct 10, 2013 at 11:24 AM, James Carman <ja...@carmanconsulting.com> wrote: > Why don't we create a real project that we can cut real releases on to > test our release procedures? Perhaps we can set it up so that it > doesn't sync with central and just gets staged locally. This way, we > can test out changes to the release process and see how they work. > Also, a new release manager can play around with that project and get > it right before diving into the real work. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
