hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14099) Split s3 testing section out into its own file
Date Mon, 20 Feb 2017 18:06:44 GMT

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

Steve Loughran updated HADOOP-14099:
    Attachment: HADOOP-14099-branch-2-001.patch

Patch 001

Testing moves to its own places, repeats our current policy w.r.t what you have to say to
get a patch reviewed, lots of detail on what we want from new testss.

* pulls testing against other s3 implementations into its own section.
* pulls out the s3:// coverage too, so that trunk can just cut that bit alone, keeping diffs
across branches to a minimum

> Split s3 testing section out into its own file
> ----------------------------------------------
>                 Key: HADOOP-14099
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14099
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: documentation, fs/s3
>    Affects Versions: 2.9.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-14099-branch-2-001.patch
> The aws/index.md file is way too big.
> We should split out the testing section into its own file, as its of relevance to developers,
not users. 
> This is also the time to clean it up and add a section on what you have to do to get
a patch reviewed, what we want from tests, etc.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message