Hi, Thank you very much Roy for this work (details below), I just tested the new website build and it looks good to me!
I added a link to https://github.com/apache/comdev-site to the footer of http://community.apache.org/ The README of https://github.com/apache/comdev-site has all the information and links on how to edit and publish the website, so from now on that URL is the only thing one needs to know to update the website. The only thing that didn't work for me is the automatic trigger of the Jenkins build after pushing my changes to https://github.com/apache/comdev-site - not sure why but manually triggering the build job worked. Thanks again Roy for your great work! -Bertrand On Tue, Mar 31, 2020 at 6:07 PM Roy Lenferink <rlenfer...@apache.org> wrote: > > I agree the PR [1] is ready to be merged (no conflicts anymore and minor > differences are resolved as > well now). Also, merging the pull requests doesn't automatically switch over > serving of community.a.o > from svn to git. It will only be served from git after [2] is merged. > > So what I'd suggest: > - merge [1], > - create a Jenkins job which updates the asf-site branch after changes to the > 'master' branch are > made (I'll do this) > - then merge [2] and start serving community.a.o from git :) > > [1] https://github.com/apache/comdev-site/pull/5 > [2] https://github.com/apache/infrastructure-puppet/pull/1753 ... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
