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

ASF GitHub Bot commented on HADOOP-18789:
-----------------------------------------

Hexiaoqiao opened a new pull request, #5800:
URL: https://github.com/apache/hadoop/pull/5800

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   Remove ozone at dev support script which has its own TLP now.
   
   ### How was this patch tested?
   No.
   
   ### For code changes:
   
   - [Y] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [N] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [N] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [N] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?




> Remove ozone from hadoop dev support
> ------------------------------------
>
>                 Key: HADOOP-18789
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18789
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Xiaoqiao He
>            Assignee: Xiaoqiao He
>            Priority: Trivial
>
> Remove ozone at dev support script which has its own TLP now.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to