Thanks, Mike, for reviewing the publishing tool last night. Here are the remaining steps I'd propose:
1) publish the site to kudu.incubator.apache.org (while still keeping the current github-hosted site) 2) if that looks good, make a new branch called 'site' starting from the current 'gh-pages' branch, which we'll use for site changes going forward. 3) make a commit to 'gh-pages' so that the getkudu.io site redirects to kudu.incubator.apache.org Does that make sense? One thing i want to make sure is that old links to getkudu.io/foo.html continue to redirect properly to kudu.incubator.apache.org/foo.html with the appropriate status code. That might not be achievable with github pages -- do we need to host our own redirect server somewhere? Maybe infra could host that for us? Any ideas? -Todd On Mon, Apr 25, 2016 at 11:56 AM, Todd Lipcon <[email protected]> wrote: > Hi folks, > > Migration of the website from github-pages to ASF gitpubsub was one item > we called out in our last podling report but haven't finished yet. > > On Friday I put up a script that will help us publish to the new > infrastructure. Would be great to get this reviewed and pushed early this > week so we can complete the migration before our report is due. > > http://gerrit.cloudera.org:8080/#/c/2856/ > > Thanks > -Todd > -- Todd Lipcon Software Engineer, Cloudera
