Hi Evans. I see three commits from your:
------------------------------------------------------------------------ r1650116 | evansye | 2015-01-07 08:48:36 -0800 (Wed, 07 Jan 2015) | 1 line Add Evans Ye to the team list ------------------------------------------------------------------------ r1650085 | evansye | 2015-01-07 07:35:39 -0800 (Wed, 07 Jan 2015) | 1 line sync up svn site's release version to git repo ------------------------------------------------------------------------ r1650010 | evansye | 2015-01-07 00:31:26 -0800 (Wed, 07 Jan 2015) | 1 line Add Evans Ye to team list I think we've been following this document here https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release check under "Build and Deploy Site" Roman, as you've have written the document Evans refers to - could you please comment if this is till relevant? I honestly am very confused about how the sites are supposed to be managed in ASF. All the changes around CMS etc are really driving me nuts. Thanks, Cos On Thu, Jan 08, 2015 at 02:30AM, Evans Ye wrote: > Hi bigtop, > > I was about to update my info on bigtop team list but got no luck. > I followed the guide here: > > https://cwiki.apache.org/confluence/display/BIGTOP/Deploying+Bigtop%27s+Apache+Website > > My local mvn site:run result was perfect, but when I went to update the > bigtop svn repo, it looked like the svn repo is out-of-date > since 2014-07-29. > The production site updated on 2014-12-04 should be the same with bigtop > git repo, but has many diff compared to svn repo. > I'm wondering is there another way to update our website without going > through https://cms.apache.org/bigtop ? > Since the production site might not be generated from svn repo. > > If someone knows how to do that, please give me a hint. > I can help to sync up the svn repo as long as it's the right way to go. > If the document is out-of-date, too, I can update the document as well.
