[jira] [Updated] (INFRA-9221) New issues@hive mailing list not getting JIRA commit messages

["Lefty Leverenz (JIRA)" <ji...@apache.org>]

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

Lefty Leverenz updated INFRA-9221:
----------------------------------
    Status: Waiting for Infra  (was: Waiting for user)

Is it okay for the reporter to change an INFRA issue's status?  (If not, I apologize.)

> New issues@hive mailing list not getting JIRA commit messages
> -------------------------------------------------------------
>
>                 Key: INFRA-9221
>                 URL: https://issues.apache.org/jira/browse/INFRA-9221
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Lefty Leverenz
>         Attachments: Screen Shot 2015-03-27 at 13.06.32.png
>
>
> The issues@hive.apache.org mailing list that was created by INFRA-9156 is missing some commit comments and status changes for Hive JIRA issues.
> Example:  HIVE-9083 had a QA comment on March 2nd, followed by Ashutosh Chauhan's comment "Committed to trunk. Thanks, Mithun!" and then a status change from Patch Available to Resolved (Version 1.2.0, Resolution Fixed), followed by some changes to Affects Version/s.  But the email list and archives only got the QA comment and Affects Version/s changes, skipping over two messages.  See archives page http://mail-archives.apache.org/mod_mbox/hive-issues/201503.mbox/thread.
> Many other Hive JIRA issues missed commit messages, such as HIVE-9509, HIVE-9731, HIVE-9803, and HIVE-9738.  But not all issues have this problem:  see HIVE-9785 and HIVE-9837 for examples that do have their commit messages in the mailing list and archives.  (Fwiw, those commits went to the CBO and LLAP branches, not trunk.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)