I wish we didn’t have to use SVN for site publication. Due to infra’s restrictions on home.apache.org <http://home.apache.org/> I had to publish the Log4j rc candidate web site at github.io <http://github.io/> instead of at people.apache.org <http://people.apache.org/> like I used to. It took me about 30 seconds to deploy. When I go to publish the site at Apache it will take me 10-20 minutes.
Ralph > On May 24, 2016, at 3:25 PM, sebb <seb...@gmail.com> wrote: > > On 24 May 2016 at 22:55, Gary Gregory <garydgreg...@gmail.com > <mailto:garydgreg...@gmail.com>> wrote: >> On Tue, May 24, 2016 at 2:51 PM, sebb <seb...@gmail.com >> <mailto:seb...@gmail.com>> wrote: >> >>> On 24 May 2016 at 21:36, Gary Gregory <garydgreg...@gmail.com >>> <mailto:garydgreg...@gmail.com>> wrote: >>>> The more this goes on the more I wish we'd switch all Commons components >>> to >>>> git lock stock and two smoking barrels. >>> >>> That would not affect GitHub, which will still be readonly. >>> >> >> Sure, but one thing I look forward to is simpler build/release/publish >> instructions. Right now, https://commons.apache.org/releases/prepare.html >> <https://commons.apache.org/releases/prepare.html> >> is getting MORE complicated because we have started adding Git instructions. > > Note that SVN is not going to go away; it will always be needed for > the DIST repo. > And probably for site publication as well. > > So there will always be a need to document both. > > However the sections which relate to the SCM are a relatively small > part of the whole and could be extracted ino separate pages for the > relevant SCM if required. > >> Gary >> >> >>> >>>> Gary >>>> On May 24, 2016 12:43 PM, <e...@zusammenkunft.net> wrote: >>>> >>>>> Hello Jochen, >>>>> >>>>> I think the announcement is refering to the Apache hosted Git >>> (writeable) >>>>> repositories (https://git-wip-us.apache.org/) - not the apache >>>>> organisation on github or the public git mirror (https://git.apache.org >>> ). >>>>> Those are always read-only mirrors. (Note that most commons projects are >>>>> still in SVN, which means there is no writeable git master repo for them >>>>> either) >>>>> >>>>> Gruss >>>>> Bernd >>>>> >>>>> -- >>>>> http://bernd.eckenfels.net >>>>> >>>>> -----Original Message----- >>>>> From: Jochen Wiedmann <jochen.wiedm...@gmail.com> >>>>> To: Commons Developers List <dev@commons.apache.org> >>>>> Cc: Commons Users List <u...@commons.apache.org>, "annou...@apache.org" >>> < >>>>> annou...@apache.org> >>>>> Sent: Di., 24 Mai 2016 12:24 >>>>> Subject: Re: [ANNOUNCE] Apache Commons git repositories now writable for >>>>> all ASF committers >>>>> >>>>> On Sat, May 21, 2016 at 5:13 PM, Benedikt Ritter <brit...@apache.org> >>>>> wrote: >>>>>> Hello, >>>>>> >>>>>> a while back, the Apache Commons project decided to grant write >>> access to >>>>>> all ASF committers [1]. While setting this up for our SVN repositories >>>>> was >>>>>> easy, we had some problems to grant the necessary karma to all ASF >>>>>> committers for our git repositories. This problem has now been fixed >>> [2]. >>>>>> All ASF committers should now be able to commit to our git >>> repositories >>>>> as >>>>>> well. This includes the repositories of the following components: >>>>>> >>>>>> - Apache Commons Lang >>>>>> - Apache Commons Math >>>>>> - Apache Commons Compress >>>>>> - Apache Commons SCXML >>>>>> >>>>>> If you experience any issues, please report them on >>>>> dev@commons.apache.org. >>>>>> >>>>>> Have fun, >>>>>> Benedikt, on behalf of the Apache Commons community >>>>>> >>>>>> [1] https://s.apache.org/RKWl >>>>>> [2] https://issues.apache.org/jira/browse/INFRA-10636 >>>>> >>>>> Doesn't work for my Github User (jochenw): >>>>> >>>>> $ git push >>>>> Username for 'https://github.com': >>>>> Password for 'https://joch...@github.com': >>>>> remote: Permission to apache/commons-fileupload.git denied to jochenw. >>>>> fatal: unable to access >>>>> 'https://github.com/apache/commons-fileupload.git/': The requested URL >>>>> returned error: 403 >>>>> >>>>> >>>>> -- >>>>> The next time you hear: "Don't reinvent the wheel!" >>>>> >>>>> >>>>> >>> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution-of-the-wheel-300x85.jpg >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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 >>>>> >>>>> >>> >>> --------------------------------------------------------------------- >>> 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 >> <http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > <mailto:dev-unsubscr...@commons.apache.org> > For additional commands, e-mail: dev-h...@commons.apache.org > <mailto:dev-h...@commons.apache.org>
