[ https://issues.apache.org/jira/browse/HADOOP-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621459#comment-16621459 ]
Junping Du commented on HADOOP-14163: ------------------------------------- echo my comments in release 2.8.5 email: "The new release web-site actually doesn't work for me. When I follow your steps in wiki, and hit the issue during git clone repository (writable) for hadoop-site as below: git clone https://gitbox.apache.org/repos/asf/hadoop-site.git Cloning into 'hadoop-site'... remote: Counting objects: 252414, done. remote: Compressing objects: 100% (29625/29625), done. remote: Total 252414 (delta 219617), reused 252211 (delta 219422) Receiving objects: 100% (252414/252414), 98.78 MiB | 3.32 MiB/s, done. Resolving deltas: 100% (219617/219617), done. warning: remote HEAD refers to nonexistent ref, unable to checkout. Can you check above repository is correct for clone? I can clone readable repository (https://github.com/apache/hadoop-site) successfully though but cannot push back changes which is expected." Can someone here reply it? 2.8.5 release work get blocked. > Refactor existing hadoop site to use more usable static website generator > ------------------------------------------------------------------------- > > Key: HADOOP-14163 > URL: https://issues.apache.org/jira/browse/HADOOP-14163 > Project: Hadoop Common > Issue Type: Improvement > Components: site > Reporter: Elek, Marton > Assignee: Elek, Marton > Priority: Major > Attachments: HADOOP-14163-001.zip, HADOOP-14163-002.zip, > HADOOP-14163-003.zip, HADOOP-14163.004.patch, HADOOP-14163.005.patch, > HADOOP-14163.006.patch, HADOOP-14163.007.patch, HADOOP-14163.008.tar.gz, > HADOOP-14163.009.patch, HADOOP-14163.009.tar.gz, HADOOP-14163.010.tar.gz, > hadoop-site.tar.gz, hadop-site-rendered.tar.gz > > > From the dev mailing list: > "Publishing can be attacked via a mix of scripting and revamping the darned > website. Forrest is pretty bad compared to the newer static site generators > out there (e.g. need to write XML instead of markdown, it's hard to review a > staging site because of all the absolute links, hard to customize, did I > mention XML?), and the look and feel of the site is from the 00s. We don't > actually have that much site content, so it should be possible to migrate to > a new system." > This issue is find a solution to migrate the old site to a new modern static > site generator using a more contemprary theme. > Goals: > * existing links should work (or at least redirected) > * It should be easy to add more content required by a release automatically > (most probably with creating separated markdown files) -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org