Team,
The only unresolved tickets against the 0.8.0 release[1] are for the
removal of code... With that in mind, does anyone object to trying to push
for this (possibly final) 0.x release?
Brandon
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%200.8
Brandon,
My concern is the language used when we published this "We support the
newest major release line (0.x, 1.x) and any previous major release
lines for up to one year since the last minor release (0.6.x, 1.5.y)
in that line" within this document [1].
If I read that now it seems like we're s
I think it is probably worth clarifying the intent of the support language.
I believe the intent was to support 0.x for a year after 1.x was released.
That was how I initially read the document you mentioned. But after a
re-read, I'd echo your concerns about dragging old major lines along.
Tony
O
Especially as nothing that would be going into the 0.x release is a major
feature or changes compatibility (from my understanding), I would +1 the 0.7.3
suggestion.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
The 0.8 fixes for licensing remove a processor (gettwitter) at this point.
That I feel requires at least minor. But avoiding that for now and doing
the bug fix things and doing 073 seems legit.
Will wait and see if anyone else has a different interpretation on the
intent of our one year version g
Based on Jira, there are 20 tickets marked as fixed in 0.8.0 and nowhere
else in the 0.x line[1]. Highlights from these include:
- NIFI-2890 - Provenance Repository corruption
- NIFI-2920 - Swapped FlowFiles are not removed from content repo when a
queue is emptied.
- NIFI-3055 - Stan
I think there's a couple considerations related to continuing the 0.x line.
First, as JoeW mentioned the Release Line Management page [1] says we
support a major release for one year, so we should plan to support 0.7.x
for one year from its July 13, 2016 release date [2].
Also, since we considere
Joe,
Just wanted to clarify that I don't believe the 1.0.0 release was a BETA.
There was a 1.0.0-BETA release on 8/5 to gather feedback and testing
from the community, and the regular 1.0.0 release on 8/26.
http://central.maven.org/maven2/org/apache/nifi/nifi-assembly/1.0.0-BETA/ (8/5)
http://c
Joe
1.0.0 was not a beta release.
1.0.0-beta was a beta release.
The intent of the language was we support the old major line for one year
once there is a major release. It is of course imperative to respect that
folks cannot migrate as quickly as we would always like. But this sort of
concern
Sorry for the confusion regarding 1.0.0-BETA vs 1.0.0, my bad.
As for stability, I don't mean build and test stability but real world
stability feedback that has led to various repository fixes including the
1.x line transition to the schema based provenance and newly refactored
provenance reposit
All,
I have started going through JIRA and identifying remaining issues against
the 0.x branch to prepare for a release, and I've worked a couple of the
JSON.org Cat-x license issues on that branch.
I would like to volunteer to be release manager for a 0.7.3 release, if you
will let me try. ;-)
Mike
You are certainly more than welcome to give the RM role a go and it is
very appreciated particularly on 0.x where it isn't as easy to put
attention/cycles.
Thanks
Joe
On Wed, Apr 12, 2017 at 6:17 PM, Michael Moser wrote:
> All,
>
> I have started going through JIRA and identifying remainin
I'll be starting to work through the release process for 0.7.3 over the
next several days, under this [1] JIRA.
-- Mike
[1] - https://issues.apache.org/jira/browse/NIFI-3824
On Sun, Apr 16, 2017 at 9:56 PM, Joe Witt wrote:
> Mike
>
> You are certainly more than welcome to give the RM role a g
Mike
it looks like there is only a single 0.7.3 ticket but there are a lot
of 0.8.0 tickets. Are you planning to cherry-pick the needed commits
into the support/0.7.x branch?
Thanks
Joe
On Thu, May 11, 2017 at 1:55 PM, Michael Moser wrote:
> I'll be starting to work through the release process
Yes indeed, I finished merging the necessary commits from 0.x into the
support/0.7.x branch. I also added the 0.7.3 Fix Version to the JIRA
tickets that were affected. I should have learned by now to do this before
sending email, haha.
Regards,
-- Mike
On Thu, May 11, 2017 at 1:57 PM, Joe Witt
15 matches
Mail list logo
