hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14025) Update CHANGES.txt for 1.2
Date Fri, 17 Jun 2016 22:29:05 GMT

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

Mikhail Antonov commented on HBASE-14025:
-----------------------------------------

[~busbey] I've been walking through the guide above looking for inspiration, and just wanted
to confirm or disprove my understandings.

 - if we're considering the Jira to be a source of truth here, then "project = HBase AND fixVersion
= 1.3.0 AND fixVersion not in (1.2.0, 1.2.1, 1.2.2) AND status in (Resolved, Closed) ORDER
BY issuetype DESC, updated ASC" jira filter should basically give the list of jiras (if we
assumed that fixVersion are set accurately), if the jira fixVersion was always accurate?
 - in the comment above:

"find the commit where your release line branched off from the previous release.
$ git merge-base 1.1.0 branch-1.2
8166142b2e815fc6ab30c14a5a546cd242bf3b4c"

But branch-1.3 was cut off branch-1 with whatever was there in the moment, so I don't see
how it applies?

> Update CHANGES.txt for 1.2
> --------------------------
>
>                 Key: HBASE-14025
>                 URL: https://issues.apache.org/jira/browse/HBASE-14025
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 1.2.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>             Fix For: 1.2.0
>
>
> Since it's more effort than I expected, making a ticket to track actually updating CHANGES.txt
so that new RMs have an idea what to expect.
> Maybe will make doc changes if there's enough here.



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

Mime
View raw message