accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-4508) Move website to its own git repo
Date Sat, 26 Nov 2016 19:00:59 GMT

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

Christopher Tubbs resolved ACCUMULO-4508.
-----------------------------------------
    Resolution: Done

> Move website to its own git repo
> --------------------------------
>
>                 Key: ACCUMULO-4508
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4508
>             Project: Accumulo
>          Issue Type: Task
>          Components: website
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>            Priority: Trivial
>
> I previously argued that gh-pages should be kept in main repo so that the "staging" repo
would be located at https://apache.github.io/accumulo and not https://apache.github.io/accumulo-website
> After seeing how little it seemed to matter for Fluo, which has a separate -website repo,
I think accumulo should do the same thing. It would help keep the main repo's branches focused
on accumulo code, and not accumulo code + extras.
> We can request a new git repo easily at https://reporeq.apache.org
> Then, we'll have to request INFRA update our site to pull from this new repo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message