hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@apache.org>
Subject Re: What to do with feature branch versions in jira
Date Thu, 26 Oct 2017 22:34:15 GMT
I try to use bulk edit to replace the version on those jiras with release
lines they went into.

Definitely should not leave feature versions open. One reason to replace
via above rather than mark released is reporter.a.o has some functionality
for pulling from jira for releases for our foundation records. Not sure if
we use that functionality though.

On Oct 26, 2017 4:14 PM, "Mike Drob" <madrob@cloudera.com> wrote:

> After a branch has been merged, what do we do with the feature branch
> version in JIRA? safe to mark it as "released" so that it doesn't show up
> in various autocompletes?
> Probably don't want to delete it because that affects the issues and maybe
> we lose track of where those commits came into? although the branch being
> the name of a jira isn't very informative anyway.
> If anybody's thought about this before, would be interested to know your
> conclusions. Otherwise, I'll go through and garden our jira a bit this
> weekend.
> Mike

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message