thanks joe . you're doing awesome at the RM thing. Not easy to rally
things together and especially difficult now as we're working the 1.x
effort in parallel.
By the way I just tried out the thing jskora put in recently for media
metadata extraction. Super cool!
On Thu, Jun 23, 2016 at 9:16 AM,
Hello Team,
Thank you all for helping finishing up all the slated 0.7.0 features.
Unfortunately I tested the 0.x branch on Windows 8 I ran into a couple issues.
Two of which are bugs in the test framework that I will fix but the third has
an unknown exact cause and is a blocker. Each of which i
I believe NIFI-1895 should be ready to go for 0.7.0 as well...
https://github.com/apache/nifi/pull/542
On Mon, Jun 20, 2016 at 11:39 AM, Joe Percivall <
joeperciv...@yahoo.com.invalid> wrote:
> Team,
>
> We are doing a great job finishing up tickets. Six more were closed over
> the weekend and m
Team,
We are doing a great job finishing up tickets. Six more were closed over the
weekend and most of the others made progress as well. We only have three more
that are tagged as 0.7.0 in Jira. There are a couple others which are
unversioned that are close but haven't been identified as import
2009 is all done (including 0.x)
Sent from my iPhone
> On Jun 17, 2016, at 14:16, Joe Percivall
> wrote:
>
> Team,
>
> We are continuing to have good progress towards the 0.7.0 release. Tagged as
> "0.7.0" in Jira and still pending, we currently have 9 tickets that are all
> patch available
Team,
We are continuing to have good progress towards the 0.7.0 release. Tagged as
"0.7.0" in Jira and still pending, we currently have 9 tickets that are all
patch available.
As a note, there seem to be a number of unversioned "patch available" tickets
in Jira. I am going to take a look at t
In another thread, I put forth the recommendation of a 0.7.1 release, for
features that don't make it in 0.7.0, but were intended to (to speed along
the 0.7.0 release).
As a consumer of NIFI, I still like that idea.
Not being part of the dev team, but assuming based on their track record,
I'm sim
I remember the thread, but it seems I need to reread the thread - honestly
the comment did take me by surprise, I think we may have used a few terms
that were left open to interpretation.
On Jun 15, 2016 5:06 PM, "Joe Skora" wrote:
> I agree with Tony on this.
>
> The point of release branching,
I agree with Tony on this.
The point of release branching, etc. is to make it possible to maintain an
older version while building the newer version. Yes, it is a nuisance, but
not nearly as much as a new version is for users if it is has significant
changes and/or bugs. Except in cases where th
Team,
There was a lot of great progress yesterday, we closed or pushed 6 tickets.
Also two tickets were added that are either critical or finishing shortly. The
status of the remaining 12 tickets are below:
- "Corrupted flow file leads to a wedged flow" NIFI-2015[1] Added yesterday.
Christophe
Tony,
I second Joe's comments as well.
Since the early discussions about the branching model I have been under the
total impression that once 1.0 is released, 0.x would become support only
and updates restricted to critical issues (security & data-loss
break-fixes).
This is not to say that a NPE
According to the discussion we had about the management of the release
lines there would only be incremental releases when something was critical
enough (security or data loss). And, if someone really wanted needed a
minor release they could initiate and do that as well. But as far as
continued f
Joe, for some reason, my mental image was that I expected we'd keep
releasing new 0.x minor releases for a while along with 1.x.
Is that everyone else's expectations?
On Jun 14, 2016 4:41 AM, "Joe Witt" wrote:
> Big thanks joe for stepping up to take on the RM tasks for the 0.7.0
> release. Ass
Big thanks joe for stepping up to take on the RM tasks for the 0.7.0
release. Assuming the 1.0.0 release happens soon this could mean that
0.7 is the last minor release in the 0.x branch!
On Mon, Jun 13, 2016 at 9:54 PM, Matt Burgess wrote:
> Andy,
> Thanks for the extra eyes on the Slack PR, I
Andy,
Thanks for the extra eyes on the Slack PR, I will look at the client auth piece
but may have some questions as I'm still hoping to "see the Matrix" on all that
security stuff :)
About to take the red pill,
Matt
P.S. To echo Andy's thoughts, thanks to Joe for organizing the release!
> On
Thanks for organizing this, Joe. I replied to Joe Witt’s question on 1795 and
removed it from 0.7.0, but Jira was down earlier so it didn’t stick. All good
now.
I’ll also throw eyes on the PutSlack PR and look forward to someone reviewing
the client auth piece. It’s small, and will be supersede
I'll take the PutSlack PR and Ricky's unpack PR, and if there's an update on
the Elasticsearch PR I'll take that too. As always though, the more eyes the
better :)
Thanks,
Matt
> On Jun 13, 2016, at 5:52 PM, Joe Percivall
> wrote:
>
> Team,
>
> Things are closing in well but we need to get
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 1.0.0
please do so. Otherwise, let's please keep discussion/st
18 matches
Mail list logo
