We may have to change our release process then. If the release fails I renamed the tag and did it again.
On Aug 29, 2014, at 4:00 PM, Matt Sicker <[email protected]> wrote: > Git won't let you change tags without doing a force push anyway, and chances > are that's disabled. If it isn't, I suggest we don't do that anyway because > it's like one of the worst things you can do with git on a shared project > (i.e., two or more developers; public or private, doesn't matter). > > > On 29 August 2014 14:53, Gary Gregory <[email protected]> wrote: > The release tag should be read only, by convention. You can branch from there > I suppose. Or just do it from trunk with the known caveat. > > Gary > > > -------- Original message -------- > From: Matt Sicker > Date:08/29/2014 14:17 (GMT-05:00) > To: Log4J Developers List > Subject: Re: Git is live > > I was going to take the 2.0.2 tag and update that. Then I can deploy a build > from there. > > > On 29 August 2014 11:41, Ralph Goers <[email protected]> wrote: > I think all the old versions of the site are still there > > Sent from my iPhone > > On Aug 29, 2014, at 8:48 AM, Gary Gregory <[email protected]> wrote: > >> The current URL is http://logging.apache.org/log4j/2.x/ >> >> but if we publish now we will publish a dev snapshot of 2.1. >> >> How about publishing more than one site, effectively archiving old releases: >> >> http://logging.apache.org/log4j/2.0 >> http://logging.apache.org/log4j/2.0.1 >> http://logging.apache.org/log4j/2.0.2 >> http://logging.apache.org/log4j/dev >> http://logging.apache.org/log4j/release- same as 2.0.2 >> >> ? >> >> Gary >> >> >> On Fri, Aug 29, 2014 at 11:43 AM, Matt Sicker <[email protected]> wrote: >> I can redeploy the website with an update this weekend. >> >> >> On 29 August 2014 10:42, Christian Grobmeier <[email protected]> wrote: >> We need to update this page: >> http://logging.apache.org/log4j/2.x/source-repository.html >> >> >> -- >> Christian Grobmeier >> [email protected] >> >> >> >> On Fri, Aug 29, 2014, at 03:59 PM, Gary Gregory wrote: >>> The Git repo is live. >>> The Svn repo is read-only. >>> >>> I am not getting commit emails from Git. How do I set that up? >>> >>> Gary >>> >>> -- >>> E-Mail: [email protected] | [email protected] >>> 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 >> >> >> >> >> -- >> Matt Sicker <[email protected]> >> >> >> >> -- >> E-Mail: [email protected] | [email protected] >> 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 > > > > -- > Matt Sicker <[email protected]> > > > > -- > Matt Sicker <[email protected]>
