This isn't to address Git. This is just in-general a little sandbox that folks can use to either test out change to the release process (or documentation) or just have a go at being a release manager before actually volunteering. Anyone would be free to cut a release at any time.
On Thu, Oct 10, 2013 at 11:34 AM, Emmanuel Bourg <ebo...@apache.org> wrote: > Le 10/10/2013 17:24, James Carman a écrit : >> 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. > > I'm not sure to see the need for this. There is no doubt Git is suitable > for releasing our components. I just walked down the release process for > JCI and besides for tagging I didn't have to interact much with SVN (I > didn't use the Maven release plugin). > > With Git you would just have to create a branch, and push a commit that > changes the version (1.0-SNAPSHOT -> 1.0). The rest of the procedure is > the same. > > Emmanuel Bourg > > > --------------------------------------------------------------------- > 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
