Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 12 Aug 2017 19:09:00 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12924386.1451191104000.19336.1502564940180@Atlassian.JIRA>
In-Reply-To: <JIRA.12924386.1451191104000@Atlassian.JIRA>
References: <JIRA.12924386.1451191104000@Atlassian.JIRA> <JIRA.12924386.1451191104020@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (HBASE-15042) refactor so that site
 materials are in the Standard Maven Place
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 12 Aug 2017 19:09:06 -0000


    [ https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124681#comment-16124681 ] 

Andrew Purtell edited comment on HBASE-15042 at 8/12/17 7:08 PM:
-----------------------------------------------------------------

I eventually had to stop copying back doc updates from master branch for 0.98 releases. I forget what broke them exactly. I think a skinning change that relied on alpha-this or beta-that maven subcomponents. We had to build with JDK6 for 0.98 and the maven binaries were incompatible at the bytecode level. If we do LTS with 1.1 on JDK7 sooner or later that can happen again. 

Unless there is a change in doc relevant for 1.1 I don't think it necessary to further update them on branch. 

We probably should update how to contribute sections in our book (for patches and doc) to call out that changes to be applied to branches which also have doc updates need the doc updates ported back. (As opposed to relying on naive copy of master docs back to branch for update.)


was (Author: apurtell):
I eventually had to stop copying back doc updates from master branch for 0.98 releases. I forget what broke them exactly. I think a skinning change that relied on alpha-this or beta-that maven subcomponents. Unless there is a change in doc relevant for 1.1 I don't think it necessary to further update them on branch. 

We probably should update how to contribute sections in our book (for patches and doc) to call out that changes to be applied to branches which also have doc updates need the doc updates ported back. (As opposed to relying on naive copy of master docs back to branch for update.)

> refactor so that site materials are in the Standard Maven Place
> ---------------------------------------------------------------
>
>                 Key: HBASE-15042
>                 URL: https://issues.apache.org/jira/browse/HBASE-15042
>             Project: HBase
>          Issue Type: Task
>          Components: build, website
>            Reporter: Sean Busbey
>            Assignee: Jan Hentschel
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE-15042.master.001.patch, HBASE-15042.master.002.patch, HBASE-15042.master.002.patch, HBASE-15042.master.003.patch
>
>
> for some reason we currently have our site materials in {{src/main/site}} rather than the maven prescribed {{src/site}}. 


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