Thanks Andy.  Will help keep up the review bandwidth as well.  Have
also taken a particular focus again as of late on our license and
notice work as we have more and more contributors/reviewers we need to
really focus there.  Will share any findings.

Thanks

On Mon, Jun 11, 2018 at 2:17 PM, Kevin Doran <kdo...@apache.org> wrote:
> This sounds like a good release plan / schedule for the upcoming versions of 
> the sub projects. Thanks, Andy.
>
>
>
> Kevin
>
>
>
> From: Andy LoPresto <alopre...@apache.org>
> Reply-To: <dev@nifi.apache.org>
> Date: Monday, June 11, 2018 at 14:03
> To: <dev@nifi.apache.org>
> Subject: Re: [DISCUSS] Release candidate timeframe for Apache NiFi 1.7.0
>
>
>
> Hi folks,
>
>
>
> With the upcoming release of Apache NiFi FDS 0.1.0 and the following release 
> of Apache NiFi Registry 0.2.0, it makes sense to hold off this release a few 
> days to get the latest versions of those projects.
>
>
>
> Here is the anticipated schedule:
>
>
>
> * 06/11 - NiFi FDS RC2 proposed
>
> * 06/14 - NiFi FDS RC2 accepted & released
>
> * 06/15 - NiFi Registry RC1 proposed
>
> * 06/18 - NiFi Registry RC1 accepted & released
>
> * 06/19 - NIFi RC1 proposed
>
> * 06/21 - NiFi RC1 accepted & released
>
>
>
> Obviously, as the version issue in FDS RC1 demonstrated, there can be 
> obstacles to overcome that may slightly affect this timeline, but I think 
> this is a reasonable expectation moving forward.
>
>
>
> As a reminder, this is the filter I am using for visibility into the close 
> out tickets. Please work with each other to get pending PRs reviewed and 
> merged quickly. Thank you.
>
>
>
> project = "Apache NiFi" AND status in ("In Progress", Reopened, "Patch 
> Available") AND updated > '2018-05-28’ ORDER BY updated DESC
>
>
>
> https://issues.apache.org/jira/issues/?filter=12344019&jql=project%20%3D%20%22Apache%20NiFi%22%20AND%20status%20in%20(%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20updated%20%3E%20%272018-05-28%27%20order%20by%20updated%20desc
>
>
>
>
>
> Andy LoPresto
>
> alopre...@apache.org
>
> alopresto.apa...@gmail.com
>
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>
>
> On Jun 11, 2018, at 7:53 AM, Joe Witt <joe.w...@gmail.com> wrote:
>
>
>
> NIFI-5022 is merged/resolved now Otto.
>
> Thanks
>
> On Mon, Jun 11, 2018 at 6:55 AM, Otto Fowler <ottobackwa...@gmail.com> wrote:
>
>
> I would really love to get a review for NIFI-5022 for this release.  Please
> let me know if there is a way to make this more likely.
>
>
>
> On June 5, 2018 at 15:09:50, Andy LoPresto (alopre...@apache.org) wrote:
>
> Sending out an update. I am using the following search query to take a look
> at what is still outstanding for 1.7.0. Currently I have visibility on the
> following issues:
>
> project = "Apache NiFi" AND (fixVersion = "1.7.0" OR (status = "Patch
> Available" AND updated > '2018-05-28')) AND status in (Open, "In Progress",
> "Reopened", "Patch Available")
>
> Patch Available (i.e. committers, please review these):
> * NIFI-5241 When calculating stats for components, use synchronized methods
> instead of atomic variables — Mark Payne
> * NIFI-5200 Nested ProcessSession.read resulting in outer stream being
> closed — Mark Payne
> * NIFI-5209 Remove toolkit migration without password functionality — Andy
> LoPresto
> * NIFI-5166 Create deep learning classification and regression processor —
> Mans Singh (Marked as In Progress but there is a PR with some comments)
> * NIFI-5226 Implement a Record API based PutInfluxDB processor — Unassigned
> (Marked as Open but there is a PR with some comments)
> * NIFI-5102 MarkLogic DB Processors — Unassigned (Marked as Open but there
> is a PR with some comments)
> * NIFI-5268 JoltTransformJSON specification property fails with EL — Koji
> Kawamura
> * NIFI-5266 PutElasticsearchHttp processors should sanitize parameters —
> Matt Burgess
> * NIFI-5263 Address auditing of Controller Service Referencing Components —
> Matt Gilman
> * NIFI-5260 Regression in nifi-processor-bundle-archetype — Bryan Bende
> * NIFI-5257 Expand Couchbase Server integration as a cache storage — Koji
> Kawamura
> * NIFI-5237 Wrong redirect from login behind a context path when using
> OpenID authentication — Matt Gilman
> * NIFI-5200 Nested ProcessSession.read resulting in outer stream being
> closed — Mark Payne
> * NIFI-5192 Allow expression language in ‘Schema File’ property for
> ValidateXML processor — Unassigned
> * NIFI-5059 MongoDBLookupService should be able to determine a schema or
> have one provided — Mike Thomsen
> * NIFI-5054 NiFi Couchbase Processors do not support User Authentication —
> Koji Kawamura
> * NIFI-5022 Create an AWS Gateway Web API version of InvokeHTTP — Otto
> Fowler
> * NIFI-4930 Nar-Dependency-Version - timestamped snapshot version problem —
> Bryan Bende
> * NIFI-1321 Support appending files in PutFile — Unassigned
>
> Reopened (i.e. Jeff, Mike, what do you need from the community to get these
> in?):
> * NIFI-5145 MockPropertyValue.evaluateExpressionLanguage(FlowFile) cannot
> handle null inputs — Mike Thomsen
> * NIFI-5175 NiFi built with Java 1.8 needs to run on Java 1.9 — Jeff Storck
>
> Open (i.e. can someone please do an s/2017/2018/ on the docs?):
> * NIFI-5106 Update docs to reflect 2018 where applicable — Aldrin Piri
>
> If anyone has other work that they are in the process of doing, please reply
> here and update the Jira appropriately. I’ll send out another summary on
> Friday. Thanks.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Jun 1, 2018, at 10:28 AM, Andy LoPresto <alopre...@apache.org> wrote:
>
> Hi folks,
>
> It’s been a little bit since 1.6.0 was released, and there have been a ton
> of new features and bug fixes that have made it in to master. With all this
> great work, I think it’s a good time to consider the next release. I
> volunteer to RM for this one.
>
> I’m thinking the next couple weeks are a good timeframe, and I wanted to put
> this out there early so anyone who is working on something they want in can
> be aware of the approaching release and communicate on the list to keep
> everyone apprised. Thanks for all your hard work.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>
>
>

Reply via email to