www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lefty Leverenz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-9221) New issues@hive mailing list not getting JIRA commit messages
Date Thu, 19 Nov 2015 05:03:11 GMT

    [ https://issues.apache.org/jira/browse/INFRA-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012799#comment-15012799

Lefty Leverenz commented on INFRA-9221:

>  Do you have the actual times/dates these commits were submitted?

I'll give you the last few examples, but of course a commit time isn't identical to the time
that the JIRA issue got updated (and a notification was sent).  These timestamps are GMT according
to the commits@hive.apache.org mailing list:

HIVE-11988 [hive] security issue with hive & ranger for import table command
* master (missing notification) -- Committed: Thu Oct 29 11:35:24 2015 -0700
* branch-1 (got the notification) -- Committed: Thu Oct 29 11:51:48 2015 -0700
* branch-1.2 (got the notification) -- Committed: Thu Oct 29 11:53:18 2015 -0700

HIVE-9013 Hive set command exposes metastore db password
* master (missing notification) -- Committed: Mon Oct 26 11:43:54 2015 -0700
* branch-1 (got the notification) -- Committed: Mon Oct 26 12:13:37 2015 -0700
* branch-1.2 (got the notification) -- Committed: Mon Oct 26 13:47:11 2015 -0700

HIVE-12187 Release plan once a query is executed 
* added 1.3.0 and 2.0.0 to Fix Version/s (missing notification) -- JIRA update was not associated
with a commit; the JIRA status change happened 15/Oct/15 18:54 but that might be in my timezone
so check for yourself
* removed 1.3.0 from Fix Version/s (got the notification) -- committed to master Fri Oct 23
09:19:54 2015 -0700

Archives for the commits@hive.apache.org mailing list are at http://mail-archives.apache.org/mod_mbox/hive-dev.
 You can find other examples there by using the date on the JIRA issue's commit comment. 
(Times won't match exactly though.)  But it seems to me you really need the update times,
which are available in the JIRA issue's Activity list -- the Comments tab doesn't include
status changes so use the All tab.

> 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
>      Security Level: public(Regular issues) 
>            Reporter: Lefty Leverenz
>            Priority: Critical
> 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

View raw message