hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Wang <andrew.w...@cloudera.com>
Subject Re: About 2.7.4 Release
Date Mon, 01 May 2017 22:53:41 GMT
On Mon, May 1, 2017 at 3:44 PM, Allen Wittenauer <aw@effectivemachines.com>

> > On May 1, 2017, at 2:27 PM, Andrew Wang <andrew.wang@cloudera.com>
> wrote:
> > I believe I asked about this on dev-yetus a while back. I'd prefer that
> the presence of the fix version be sufficient to indicate whether a JIRA is
> included in a release branch. Yetus requires that the JIRA be resolved as
> "Fixed" to show up, which is why we are in our current situation.
>         We can't do this because Hadoop is the only one that I've seen
> that sets Fix version at close time.  Everyone else is setting fix version
> in place of target (which is a custom field, iirc).
> Let's see if I can revive the discussion over on a yetus list/jira. I
think it's easier to add a new flag to Yetus than changing the Hadoop JIRA
workflow, and it seems like this issue is becoming more acute.

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