nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brandon DeVries <...@jhu.edu>
Subject Re: [DISCUSS} Closing in on a NiFi 1.4.0 release?
Date Mon, 18 Sep 2017 18:28:45 GMT
There are significant changes in 1.4.0 that I am actively waiting on...

On Mon, Sep 18, 2017 at 2:25 PM Russell Bateman <russ@windofkeltia.com>
wrote:

> I don't know. Are we due for a release? Is time-since the significant
> factor in a release cycle or is growing features part of it?
>
> 1.3.0 subsists with no bump of the third digit. This is an oddly stable
> .0 product (though the third digit had somewhat different semantics in
> NiFi 0.x). No bug fixes to 1.3.0 in its roughly 6-month history? That's
> an achievement.
>
> If there have been important features worked on and ready to go, by all
> means, let's have 1.4.0. But if 1.4.0 is little more than 1.3.1, let's
> rethink why we'd do that.
>
> Russ
>
>
> On 09/18/2017 12:08 PM, Brandon DeVries wrote:
> > +1, it seems like we're do for a release.  It's been a week, and a couple
> > of the mentioned tickets have shown progress... but a number haven't.  If
> > no one wants to get them wrapped up, can we put them off to 1.5?
> >
> > On Mon, Sep 11, 2017 at 11:39 AM Wes Lawrence <wesleyll505@gmail.com>
> wrote:
> >
> >> I'd also like NIFI-4242 and NIFI-4181 added (or if it's OK, I can label
> >> their fix versions for 1.4.0. I wasn't sure sure I could do that, or if
> >> that should be left to PMC/Commiters)
> >>
> >> NIFI-4242 <https://issues.apache.org/jira/browse/NIFI-4242> has a patch
> >> with feedback, and I'll be pushing a new patch addressing the feedback
> >> later today.
> >> NIFI-4181 <https://issues.apache.org/jira/browse/NIFI-4181> has a patch
> >> with feedback, and I'd like to address the feedback for 1.4.0 if
> possible.
> >>
> >> --Wes
> >>
> >> On Mon, Sep 11, 2017 at 10:33 AM, Christopher Currie <
> >> christopher@currie.com
> >>> wrote:
> >>> In addition to this list, I'd like to request that
> >>> https://issues.apache.org/jira/browse/NIFI-3950 also be added. I
> >> created a
> >>> PR for it, and I'm happy to work with a committer to clean it up for
> >>> project standards if needed.
> >>>
> >>> Christopher
> >>> On Mon, Sep 11, 2017 at 6:44 AM James Wing <jvwing@gmail.com> wrote:
> >>>
> >>>> +1  It does seem to be about time to get a release out, and we should
> >>>> certainly take advantage of your offer to performing RM duties.  Thank
> >>> you
> >>>> for that.
> >>>>
> >>>> On Sun, Sep 10, 2017 at 5:45 PM, Jeff <jtswork@gmail.com> wrote:
> >>>>
> >>>>> All,
> >>>>>
> >>>>> On the dev and users lists there have been some questions about
when
> >>> the
> >>>>> next release of NiFi would be.  I would like perform RM duties,
and
> >> get
> >>>>> things started on identifying what the community would like to
> >> include
> >>> in
> >>>>> the release of NiFi 1.4.0 that has not already been reviewed and
> >>>> committed
> >>>>> to master.
> >>>>>
> >>>>> There are 11 unresolved JIRAs tagged with a fix version of 1.4.0.
> >>>>>
> >>>>> https://issues.apache.org/jira/issues/?jql=project%20%
> >>>>> 3D%20NIFI%20AND%20resolution%20%3D%20Unresolved%20AND%
> >>>>> 20fixVersion%20%3D%201.4.0%20ORDER%20BY%20priority%
> >>> 20DESC%2C%20key%20DESC
> >>>>> Are there any reasons to hold off on a 1.4.0 release?  Are there
> >>>> particular
> >>>>> JIRAs that the community considers necessary to have as part of
the
> >>>>> release? Let's discuss!
> >>>>>
> >>>>> Thanks,
> >>>>> Jeff
> >>>>>
>
>

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