[
https://issues.apache.org/jira/browse/HBASE-14025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617122#comment-14617122
]
Sean Busbey commented on HBASE-14025:
-------------------------------------
{quote}
I think I get your point, but not sure how easily we can follow this practice.
It gets complicated for committers to think about what fixVersions to set at
the time of the commit. The thing we have where we just mark the next scheduled
version from that branch is simple and worked so far.
{quote}
That's fair. I think this is the kind of thing that release managers will have
to do, since they know if something actually made it into the release branch.
Since it's one time work on non-patch releases it doesn't seem so bad.
I see it the same as how when the RCs get close the RM needs to move out things
that aren't going to make it in (e.g. replacing a 1.2.0 version with 1.2.1 and
1.3.0) or move back in things that got committed between candidates (e.g. by
replacing 1.2.1 with 1.2.0).
{quote}
Can we do a middle ground where we keep the fixVersions in jira, and filter
them out in CHANGES.txt for convenience if not needed?
{quote}
The problem with this is that then the release notes in Jira will be less
accurate than the CHANGES.txt file, and I'd very much like to point to the jira
data as authoritative.
What about having the committers continue with their current habit and then
leaving it to the release managers to make things consistent around release
time?
> 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)
