[jira] [Commented] (HDDS-1659) Define the process to add proposal/design docs to the Ozone subproject

2019-08-13 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HDDS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906765#comment-16906765
 ] 

Hudson commented on HDDS-1659:
--

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17110 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/17110/])
HDDS-1659. Define the process to add proposal/design docs to the Ozone 
(aengineer: rev 50a22b66c0292d37984460991a680d9d3e8c862c)
* (add) hadoop-hdds/docs/content/design/ozone-enhancement-proposals.md


> Define the process to add proposal/design docs to the Ozone subproject
> --
>
> Key: HDDS-1659
> URL: https://issues.apache.org/jira/browse/HDDS-1659
> Project: Hadoop Distributed Data Store
>  Issue Type: Task
>Reporter: Elek, Marton
>Assignee: Elek, Marton
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.5.0
>
>  Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> We think that it would be more effective to collect all the design docs in 
> one place and make it easier to review them by the community.
> We propose to follow an approach where the proposals are committed to the 
> hadoop-hdds/docs project and the review can be the same as a review of a PR



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Commented] (HDDS-1659) Define the process to add proposal/design docs to the Ozone subproject

2019-06-12 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HDDS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861806#comment-16861806
 ] 

Hudson commented on HDDS-1659:
--

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16729 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16729/])
Revert "HDDS-1659. Define the process to add proposal/design docs to the (elek: 
rev 23c037906f7aa4912fe89724750b2d634d37f231)
* (delete) hadoop-hdds/docs/content/design/ozone-enhancement-proposals.md


> Define the process to add proposal/design docs to the Ozone subproject
> --
>
> Key: HDDS-1659
> URL: https://issues.apache.org/jira/browse/HDDS-1659
> Project: Hadoop Distributed Data Store
>  Issue Type: Task
>Reporter: Elek, Marton
>Assignee: Elek, Marton
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.4.1
>
>  Time Spent: 2h
>  Remaining Estimate: 0h
>
> We think that it would be more effective to collect all the design docs in 
> one place and make it easier to review them by the community.
> We propose to follow an approach where the proposals are committed to the 
> hadoop-hdds/docs project and the review can be the same as a review of a PR



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Commented] (HDDS-1659) Define the process to add proposal/design docs to the Ozone subproject

2019-06-11 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/HDDS-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861346#comment-16861346
 ] 

Hudson commented on HDDS-1659:
--

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16725 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16725/])
HDDS-1659. Define the process to add proposal/design docs to the Ozone 
(aengineer: rev e997f2a34a170dfcd1023b82d1ced85c46b0f1f1)
* (add) hadoop-hdds/docs/content/design/ozone-enhancement-proposals.md


> Define the process to add proposal/design docs to the Ozone subproject
> --
>
> Key: HDDS-1659
> URL: https://issues.apache.org/jira/browse/HDDS-1659
> Project: Hadoop Distributed Data Store
>  Issue Type: Task
>Reporter: Elek, Marton
>Assignee: Elek, Marton
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.4.1
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> We think that it would be more effective to collect all the design docs in 
> one place and make it easier to review them by the community.
> We propose to follow an approach where the proposals are committed to the 
> hadoop-hdds/docs project and the review can be the same as a review of a PR



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org