infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (INFRA-14700) Move BookKeeper Website from CMS to gitpubsub
Date Thu, 27 Jul 2017 18:46:00 GMT


ASF subversion and git services commented on INFRA-14700:

Commit 945ef597dc5f0029e3e27faa45af3d0804d6d924 in infrastructure-puppet's branch refs/heads/pono/INFRA-14700
from [~pono]
[;h=945ef59 ]

INFRA-14700 bookkeeper test repo

> Move BookKeeper Website from CMS to gitpubsub
> ---------------------------------------------
>                 Key: INFRA-14700
>                 URL:
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Website
>            Reporter: Sijie Guo
>            Assignee: Daniel Takamori
> 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:
> 2) Make{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

View raw message