nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aldrin Piri <aldrinp...@gmail.com>
Subject Re: Closing in on the Apache NiFi 0.6.0 release
Date Mon, 21 Mar 2016 17:42:21 GMT
All,

It looks like the last ticket for 0.6.0 has been merged and resolved.

I will begin the RC process shortly working off of commit
736896246cf021dbed31d4eb1e22e0755e4705f0 [1] [2].

[1]
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=736896246cf021dbed31d4eb1e22e0755e4705f0
[2]
https://github.com/apache/nifi/commit/736896246cf021dbed31d4eb1e22e0755e4705f0

On Mon, Mar 21, 2016 at 1:48 AM, Tony Kurc <trkurc@gmail.com> wrote:

> The Locale issue was reviewed, confirmed as fixed by reporter and merged
> in.
>
> On Sun, Mar 20, 2016 at 10:35 PM, Joe Witt <joe.witt@gmail.com> wrote:
>
> > Team,
> >
> > There are a couple finishing touches PRs to fix a big defect in
> > SplitText for certain input types, improve locale handling and test
> > behavior for Kit bundle, and to clean up content viewing from
> > connections.
> >
> > Getting good input on findings folks have so please keep it coming as
> > that helps ensure a solid/healthy RC.
> >
> > Thanks
> > Joe
> >
> > On Sat, Mar 19, 2016 at 6:21 PM, Tony Kurc <trkurc@gmail.com> wrote:
> > > Recommend https://issues.apache.org/jira/browse/NIFI-1651 be included
> in
> > > 0.6.0
> > >
> > > On Wed, Mar 16, 2016 at 4:08 PM, Joe Witt <joe.witt@gmail.com> wrote:
> > >
> > >> Team,
> > >>
> > >> Ok sooo close.  We have 5 tickets remaining.
> > >>
> > >> - Additional functionality/cleanup for SplitText [1]
> > >> [status] Still in discussions. Recommend we move this change to 0.7.0.
> > >> Solid effort on both code contributor and reviewer side but this is a
> > >> tricky one.
> > >>
> > >> - Support Kerberos based authentication to REST API [2]
> > >> [status] PR is in. Reviewing and PR tweaking appears active.  Looks
> > >> quite close and comments indicate great results.
> > >>
> > >> - Add Kerberos support to HBase processors [3]
> > >> [status] Patch in. Under review.  Running on live test system with
> > >> great results.
> > >>
> > >> - Add support for Spring Context loaded processors (Spring
> > >> Integrations, Camel, ...) [4]
> > >> [status] Appears ready. Getting review feedback.
> > >>
> > >> - Zookeeper interaction for NiFI state management should limit state
> to
> > >> 1MB [6]
> > >> [status] Patch is in and review under way.  Looks close.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/NIFI-1118
> > >> [2] https://issues.apache.org/jira/browse/NIFI-1274
> > >> [3] https://issues.apache.org/jira/browse/NIFI-1488
> > >> [4] https://issues.apache.org/jira/browse/NIFI-1571
> > >> [5] https://issues.apache.org/jira/browse/NIFI-1626
> > >>
> > >> Thanks
> > >>
> > >> On Wed, Mar 16, 2016 at 4:04 PM, Joe Witt <joe.witt@gmail.com> wrote:
> > >> > Team,
> > >> >
> > >> > Ok sooo close.  We have 6 tickets remaining.
> > >> >
> > >> > - Additional functionality/cleanup for SplitText [1]
> > >> > [status] Still in discussions. Recommend we move this change to
> 0.7.0.
> > >> > Solid effort on both code contributor and reviewer side but this is
> a
> > >> > tricky one.
> > >> >
> > >> > - Support Kerberos based authentication to REST API [2]
> > >> > [status] PR is in. Reviewing and PR tweaking appears active.  Looks
> > >> > quite close and comments indicate great results.
> > >> >
> > >> > - Add Kerberos support to HBase processors [3]
> > >> > [status] Patch in. Under review.  Running on live test system with
> > >> > great results.
> > >> >
> > >> > - Add support for Spring Context loaded processors (Spring
> > >> > Integrations, Camel, ...) [4]
> > >> > [status] Appears ready. Getting review feedback.
> > >> >
> > >> > - Support based database snapshot/query/change capture [5]
> > >> > [status] Appears ready. Needs review.
> > >> >
> > >> > - Zookeeper interaction for NiFI state management should limit state
> > to
> > >> 1MB [6]
> > >> > [status] Patch is in and review under way.  Looks close.
> > >> >
> > >> > [1] https://issues.apache.org/jira/browse/NIFI-1118
> > >> > [2] https://issues.apache.org/jira/browse/NIFI-1274
> > >> > [3] https://issues.apache.org/jira/browse/NIFI-1488
> > >> > [4] https://issues.apache.org/jira/browse/NIFI-1571
> > >> > [5] https://issues.apache.org/jira/browse/NIFI-1575
> > >> > [6] https://issues.apache.org/jira/browse/NIFI-1626
> > >> >
> > >> > Thanks
> > >> > Joe
> > >> >
> > >> > On Tue, Mar 15, 2016 at 11:56 AM, Aldrin Piri <aldrinpiri@gmail.com
> >
> > >> wrote:
> > >> >> Sounds great.  Will scope those out in the process.  Thanks, Tony.
> > >> >>
> > >> >> On Tue, Mar 15, 2016 at 11:37 AM, Tony Kurc <trkurc@gmail.com>
> > wrote:
> > >> >>
> > >> >>> Aldrin,
> > >> >>> I did some crappy shell scripts to help, I'll try to put those
up
> on
> > >> the
> > >> >>> wiki.
> > >> >>>
> > >> >>> Tony
> > >> >>>
> > >> >>> On Tue, Mar 15, 2016 at 11:29 AM, Aldrin Piri <
> aldrinpiri@gmail.com
> > >
> > >> >>> wrote:
> > >> >>>
> > >> >>> > In an effort to avoid me missing helpers and spamming
the list,
> I
> > >> will
> > >> >>> > throw my hat into the ring to do this one.
> > >> >>> >
> > >> >>> > On Tue, Mar 15, 2016 at 11:28 AM, Joe Witt <joe.witt@gmail.com>
> > >> wrote:
> > >> >>> >
> > >> >>> > > Team,
> > >> >>> > >
> > >> >>> > > Seeing good progress today.  Great!
> > >> >>> > >
> > >> >>> > > I know I volunteered to do the RM for the release
but now I
> need
> > >> to be
> > >> >>> > > out of town and will have questionable Internet
access.  Can
> > >> someone
> > >> >>> > > else grab it?
> > >> >>> > >
> > >> >>> > > Thanks
> > >> >>> > > Joe
> > >> >>> > >
> > >> >>> > > On Mon, Mar 14, 2016 at 9:01 PM, Joe Witt <joe.witt@gmail.com
> >
> > >> wrote:
> > >> >>> > > > Team,
> > >> >>> > > >
> > >> >>> > > > Things are closing in well but we need to get
pretty
> specific
> > on
> > >> >>> these
> > >> >>> > > > to keep the release moving roughly along the
lines of the
> > >> schedule
> > >> >>> > > > we've discussed previously.  Those of you who
have tickets
> on
> > >> here
> > >> >>> > > > that can be moved to 0.7.0 please do so.  Otherwise,
let's
> > please
> > >> >>> keep
> > >> >>> > > > discussion/status information up so we can
all see how we're
> > >> trending
> > >> >>> > > > toward release candidate readiness.
> > >> >>> > > >
> > >> >>> > > > The current items on the release based on JIRA
fix version
> > that
> > >> >>> remain
> > >> >>> > > are:
> > >> >>> > > >
> > >> >>> > > > - Supporting a new JMS producer/consumer style
[1] [2] [3]
> > >> >>> > > > [status]Great rounds of review with Oleg, Percivall,
Moser.
> > >> Looks
> > >> >>> > close.
> > >> >>> > > >
> > >> >>> > > > - Processors to interact with Apache Cassandra
[4]
> > >> >>> > > > [status]Looks ready but needing review.
> > >> >>> > > >
> > >> >>> > > > - Additional functionality/cleanup for SplitText
[5]
> > >> >>> > > > [status]Still in discussions.  Recommend we
move this change
> > to
> > >> >>> 0.7.0.
> > >> >>> > > >
> > >> >>> > > > - Support Kerberos based authentication to
REST API [6]
> > >> >>> > > > [status]Update suggests it is almost ready.
 A suggested key
> > >> feature
> > >> >>> > > > of this release.
> > >> >>> > > >
> > >> >>> > > > - Add Kerberos support to HBase processors
[7]
> > >> >>> > > > [status]Appears nearly ready.  Great discussions
and group
> > >> contribs.
> > >> >>> > > >
> > >> >>> > > > - Add support for Spring Context loaded processors
(Spring
> > >> >>> > > > Integrations, Camel, ...) [8]
> > >> >>> > > > [status]Appears ready.  Needs review.
> > >> >>> > > >
> > >> >>> > > > - Support based database snapshot/query/change
capture [9]
> > >> >>> > > > [status] Appears ready.  Needs review.
> > >> >>> > > >
> > >> >>> > > > - Allow empty content posting w/o content type
header [10]
> > >> >>> > > > [status] Discussions led to changing behavior
a bit.
> Possibly
> > >> slide
> > >> >>> > > > to 0.7.0 as an alternative approach exists
for now.
> > >> >>> > > >
> > >> >>> > > > - Support Kinesis Firehose interaction [11]
> > >> >>> > > > [status] Appears to be a candidate to slide
to 0.7.0
> > >> >>> > > >
> > >> >>> > > > - Support Apache Spark 1.6 for Spark receiver
[12]
> > >> >>> > > > [status] Appears ready but needing review.
> > >> >>> > > >
> > >> >>> > > > - Support SSL with AMQP processors [13]
> > >> >>> > > > [status] Appears ready but needs review as
it adds to a
> > commonly
> > >> used
> > >> >>> > > > SSL interface.
> > >> >>> > > >
> > >> >>> > > > [1] https://issues.apache.org/jira/browse/NIFI-614
> > >> >>> > > > [2] https://issues.apache.org/jira/browse/NIFI-1424
> > >> >>> > > > [3] https://issues.apache.org/jira/browse/NIFI-1425
> > >> >>> > > > [4] https://issues.apache.org/jira/browse/NIFI-901
> > >> >>> > > > [5] https://issues.apache.org/jira/browse/NIFI-1118
> > >> >>> > > > [6] https://issues.apache.org/jira/browse/NIFI-1274
> > >> >>> > > > [7] https://issues.apache.org/jira/browse/NIFI-1488
> > >> >>> > > > [8] https://issues.apache.org/jira/browse/NIFI-1571
> > >> >>> > > > [9] https://issues.apache.org/jira/browse/NIFI-1575
> > >> >>> > > > [10] https://issues.apache.org/jira/browse/NIFI-1620
> > >> >>> > > > [11] https://issues.apache.org/jira/browse/NIFI-1495
> > >> >>> > > > [12] https://issues.apache.org/jira/browse/NIFI-1519
> > >> >>> > > > [13] https://issues.apache.org/jira/browse/NIFI-1521
> > >> >>> > > >
> > >> >>> > > > On Thu, Mar 10, 2016 at 2:10 PM, Joe Witt <
> joe.witt@gmail.com
> > >
> > >> >>> wrote:
> > >> >>> > > >> Have updated the migration guide [1] and
release notes [2]
> > for
> > >> >>> 0.6.0.
> > >> >>> > > >> If there are features/inclusions will adjust
as needed.  I
> > >> intend to
> > >> >>> > > >> follow a very similar RM model to what
Tony did for the
> 0.5.x
> > >> line
> > >> >>> and
> > >> >>> > > >> which follows the apparent consensus from
our recent Git
> > >> >>> discussions.
> > >> >>> > > >>
> > >> >>> > > >> We'll definitely need folks to really focus
in on the
> > existing
> > >> JIRAs
> > >> >>> > > >> slated for 0.6.0 and any necessary reviews
or tweaks.
> Early
> > >> next
> > >> >>> week
> > >> >>> > > >> we should start moving tickets to the next
minor (0.7.0)
> > build
> > >> that
> > >> >>> > > >> aren't key bug fixes or aren't tied to
previously stated
> > 0.6.0
> > >> >>> goals.
> > >> >>> > > >>
> > >> >>> > > >> [1]
> > >> >>> >
> > https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
> > >> >>> > > >> [2]
> > >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes
> > >> >>> > > >>
> > >> >>> > > >> Thanks
> > >> >>> > > >> Joe
> > >> >>> > > >>
> > >> >>> > > >> On Wed, Mar 9, 2016 at 6:08 PM, Tony Kurc
<
> trkurc@gmail.com>
> > >> wrote:
> > >> >>> > > >>> Joe,
> > >> >>> > > >>> I tagged this one that I've been closing
in on, and was
> just
> > >> >>> > finishing
> > >> >>> > > up.
> > >> >>> > > >>>
> > >> >>> > > >>> https://issues.apache.org/jira/browse/NIFI-1481
> > >> >>> > > >>>
> > >> >>> > > >>> On Wed, Mar 9, 2016 at 5:42 PM, Joe
Witt <
> > joewitt@apache.org>
> > >> >>> wrote:
> > >> >>> > > >>>
> > >> >>> > > >>>> Team,
> > >> >>> > > >>>>
> > >> >>> > > >>>> It is time to start pulling in
for the Apache NiFi 0.6.0
> > >> release
> > >> >>> to
> > >> >>> > > >>>> keep with our previously suggested
cadence.  There are
> > >> already a
> > >> >>> lot
> > >> >>> > > >>>> of really nice improvements/bug
fixes on there and some
> > nice
> > >> new
> > >> >>> > > >>>> features.  We do have about 23
outstanding JIRAs assigned
> > >> that are
> > >> >>> > > >>>> open.
> > >> >>> > > >>>>
> > >> >>> > > >>>> Most appear to be in great shape
with active discussion
> > >> centered
> > >> >>> > > >>>> around PRs with review feedback.
 Some just appear to
> need
> > the
> > >> >>> final
> > >> >>> > > >>>> push over the merge line.  There
are also some PRs on
> > Github
> > >> that
> > >> >>> > may
> > >> >>> > > >>>> well be in a ready state.
> > >> >>> > > >>>>
> > >> >>> > > >>>> If there are things which are really
important to folks
> > that
> > >> they
> > >> >>> do
> > >> >>> > > >>>> not presently see on the 0.6.0
list but that they really
> > >> want/need
> > >> >>> > and
> > >> >>> > > >>>> think are ready or close to ready
please advise.
> > >> >>> > > >>>>
> > >> >>> > > >>>> I am happy to RM the release but
if someone else is
> > interested
> > >> >>> > please
> > >> >>> > > >>>> advise.  Let's try to shoot for
Mar 16th vote start so we
> > can
> > >> be
> > >> >>> > close
> > >> >>> > > >>>> to the Mar 18th goal talked about
a while ago on the 6-12
> > >> month
> > >> >>> > > >>>> roadmap proposal.
> > >> >>> > > >>>>
> > >> >>> > > >>>> Thanks
> > >> >>> > > >>>> Joe
> > >> >>> > > >>>>
> > >> >>> > >
> > >> >>> >
> > >> >>>
> > >>
> >
>

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