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

Hudson commented on HBASE-19230:
--------------------------------

Results for branch branch-2.1
        [build #1361 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1361/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1361//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- Something went wrong running this stage, please [check relevant console 
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1361//console].


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1361//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Write up fixVersion policy from dev discussion in refguide
> ----------------------------------------------------------
>
>                 Key: HBASE-19230
>                 URL: https://issues.apache.org/jira/browse/HBASE-19230
>             Project: HBase
>          Issue Type: Task
>          Components: documentation
>            Reporter: stack
>            Assignee: Murtaza Hassan
>            Priority: Major
>              Labels: beginner
>             Fix For: 3.0.0, 1.5.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6, 1.3.6, 1.4.11
>
>
> Useful discussion up on dev list "Fix version maintenance for 1.4.0" where we 
> state fixVersion in JIRA policy we all seem to be following but have never 
> written down anywhere. This issue is about synopsizing what came of the 
> discussion in the refguide dev/RM section.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to