infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Takamori (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-14700) Move BookKeeper Website from CMS to gitpubsub
Date Wed, 26 Jul 2017 18:44:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-14700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Takamori updated INFRA-14700:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

> Move BookKeeper Website from CMS to gitpubsub
> ---------------------------------------------
>
>                 Key: INFRA-14700
>                 URL: https://issues.apache.org/jira/browse/INFRA-14700
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Website
>            Reporter: Sijie Guo
>
> BookKeeper website/documentation is based on CMS. The community is developing a new Jekyll
website (to easily manage both website/documentation source files along with source code),
and decides to move from CMS to gitpubsub.
> We'd like to see if following approach is doable:
> 1) Enable gitpubsub in apache bookkeeper repo: https://github.com/apache/bookkeeper
> 2) Make http://bookkeeper.apache.org/docs/r{version}/ still point to the existing CMS
content for old releases' documentation
> This allows the co-exists of old documentation for old releases and new website/documentation
for new releases for a while. We will slowly phase out the old releases and remove the old
documentation from CMS.
> Does this solution work? If it doesn't work, is there any suggestions from INFRA?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message