When looking at that code for the page, I had thought that perhaps would not hard-code the year, but would use a javascript function to get the date/year and include that when the site gets rendered -- but that makes sense in my head, which easily doesn't translate to being easy-to-impliment.
On Sun, Feb 16, 2020 at 1:39 PM Tomasz Urbaszek <turbas...@apache.org> wrote: > Thanks for the quick response! It seems that https://www.apache.org is > also little bit out of date (2019 instead of 2020). Is there any > possibility to use some auto-update? > > T. > > > On Sun, Feb 16, 2020 at 3:51 PM Shane Curcuru <a...@shanecurcuru.org> > wrote: > > > > Roy Lenferink wrote on 2020-2-16 6:34AM EST: > > > Following the WEBSITE-HOWTO [1] I just updated the year from 2018 to > 2020. > > > However, a comdev-er still needs to publish the site [2] as I was > unable to. > > > "svnmucc: E175013: Access to > > > > '/repos/infra/!svn/txr/1056611-mpm7/websites/production/community/content' > > > forbidden" > > > > Done! Excellent instructions, I had forgotten about the cms publish > > links. Thanks to Tomasz for reporting. > > > > > [1] https://github.com/apache/comdev-site/blob/trunk/WEBSITE-HOWTO.txt > > > [2] https://cms.apache.org/community/publish?diff=1 > > > > -- > > > > - Shane > > Comdev PMC > > The Apache Software Foundation > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
