Re: NiFi Boot Error

2019-04-04 Thread Andy LoPresto 
Bimal, 

The sensitive keys property specifies a raw value from which the encryption key 
for sensitive component properties is derived. This is used to protect things 
like a database password, AWS credentials, etc. that you configure in your 
flows when they are persisted to the file system. You should populate this 
property with a long and unique value in your nifi.properties file. 

This is documented in the Admin Guide [1][2]. If you have an existing flow with 
sensitive properties already encrypted using the default empty key, you can 
migrate them using the NiFi Encrypt Config Toolkit [3]. 

[1] 
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#how-to-install-and-start-nifi
 

[2] 
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#security_properties
 

[3] 
https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#encrypt_config_tool
 





Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Apr 4, 2019, at 9:43 AM, Bimal Mehta  wrote:
> 
> I recently upgraded to NiFi 1.9.0.
> However on starting the NiFi service I get the following error
> 
> A blank sensitive properties key was provided
> Specify a unique key in nifi.properties for nifi.sensitive.props.key
> 
> I am not sure about this property. What do I need to do?
> 
> Thanks
> Bimal Mehta

Re: [VOTE] Release Apache NiFi 1.9.2 (rc2)

2019-04-04 Thread Andy LoPresto 
+1, binding

Downloaded, verified signature and checksums, built with contrib check, all 
tests pass. 

Ran application and performed smoke tests. 

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Apr 4, 2019, at 9:11 AM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.9.2.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-
> 
> The Git tag is nifi-1.9.2-RC2
> The Git commit ID is 11320acfbaab1a3579bd8f7545473d6984472d77
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=11320acfbaab1a3579bd8f7545473d6984472d77
> 
> Checksums of nifi-x.y.z-source-release.zip:
> SHA256: 1f666c30171e2b7be847a3a852e9176420fd0176537f3ce6428b786a6d24f456
> SHA512:
> f65b81976a9811017348f9e8340faff3a29b029878845dd509db98eb7449752c8ef0bdbf5d1f67635636bb08be28086015442f546821eebf76b499cebf1a386b
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 11 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345213
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.2
> 
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
> 
> [ ] +1 Release this package as nifi-1.9.2
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: [DISCUSS] NiFi and Java 11

2019-04-04 Thread Kevin Doran 
Jeff,

Thanks for all your work on this and for explaining the path forward.
I also support this proposal.

I suggest we take the same basic approach for NiFi Registry. That is:

- For the current NiFi Registry 0.x line, we maintain Java 8 and 11
build compatibility
- We perform Java 8 builds (that can run on 8 and 11) for our
convenience binaries
- We plan to bump the major version at some point in the future in
step with NiFi which will move us to requiring Java 11 for Registry as
well

I've looked at your PRs, and I think getting NiFi Registry to the
point that it can run on Java 11 will be much easier than NiFi was
given it is a much smaller and simpler project, and it will mostly
require a subset of the changes you made for NiFi (Groovy, JaxB
dependencies for example).

Thanks,
Kevin

On Thu, Apr 4, 2019 at 12:54 PM Matt Gilman  wrote:
>
> Jeff,
>
> I think this is a great approach that should help us transition to and in
> the long run, adopt Java 11. The staggered approach should allow us to
> address concerns and any issues we may encounter as we go over time.
>
> Thanks for putting these together!
>
> Matt
>
> On Thu, Apr 4, 2019 at 2:19 AM Jeff  wrote:
>
> > I created a JIRA [1] to track the developer documentation changes.  Andy,
> > thanks for pointing out the specific links; I've added them to the JIRA.
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-6187
> >
> > On Wed, Apr 3, 2019 at 11:23 PM Sivaprasanna 
> > wrote:
> >
> > > Yep. Adding to GitHub template is a great idea.
> > >
> > > On Thu, 4 Apr 2019 at 5:27 AM, Andy LoPresto 
> > wrote:
> > >
> > > > We should add that to the Developer Guide [1], Contributor Guide [2],
> > > note
> > > > it in the Migration Guide [3] when it takes effect, and include it in
> > the
> > > > GitHub PR template as well.
> > > >
> > > > [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html <
> > > > https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html>
> > > > [2] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
> > <
> > > > https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide>
> > > > [3]
> > https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
> > > <
> > > > https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance>
> > > >
> > > >
> > > > Andy LoPresto
> > > > alopre...@apache.org
> > > > alopresto.apa...@gmail.com
> > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > > >
> > > > > On Apr 3, 2019, at 1:16 PM, Sivaprasanna 
> > > > wrote:
> > > > >
> > > > > Sounds good to me.
> > > > >
> > > > > So contributors who bring in new changes are expected to write the
> > code
> > > > > that should be compatible with both Java 8 as well as Java 11, right?
> > > > >
> > > > > Do we see anything that we should have in our site that would help
> > the
> > > > > contributors/users with this change? Something like a document that
> > > > > explains best practices which a developer should follow so that the
> > > > change
> > > > > which the developer is bringing in should run fine in both 8 and 11.
> > > > >
> > > > > -
> > > > > Sivaprasanna
> > > > >
> > > > > On Thu, 4 Apr 2019 at 12:18 AM, Pierre Villard <
> > > > pierre.villard...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Sounds good to me as well. Given the latest news on Java 8, having
> > > the 2
> > > > >> PRs merged in would be great!
> > > > >>
> > > > >> Thanks,
> > > > >> Pierre
> > > > >>
> > > > >> Le mer. 3 avr. 2019 à 20:34, Joe Witt  a écrit
> > :
> > > > >>
> > > > >>> Jeff
> > > > >>>
> > > > >>> This seems very reasonable and thorough to me.
> > > > >>>
> > > > >>> The only short term implication that we'd have to buy into then is
> > > that
> > > > >> PRs
> > > > >>> going forward need to be able to build on both Java 8 and 11 which
> > > > seems
> > > > >> a
> > > > >>> very fair way to bridge toward moving to Java 11 as the base
> > > > requirement
> > > > >> in
> > > > >>> the next major release of NiFi (2.x).
> > > > >>>
> > > > >>> Thanks
> > > > >>> Joe
> > > > >>>
> > > > >>> On Wed, Apr 3, 2019 at 2:19 PM Jeff  wrote:
> > > > >>>
> > > >  I'm reaching out to the community today to propose a plan for
> > moving
> > > >  forward with NiFi on Java 11.
> > > > 
> > > >  There are currently two PRs that deal with Java 11 compatibility.
> > > The
> > > >  first PR allows NiFi built on Java 8 to be run on Java 11 [1].
> > The
> > > > >>> second
> > > >  PR allows NiFi to be built on Java 11 and run on Java 11 [2].
> > There
> > > > >> are
> > > > >>> a
> > > >  lot of changes in the second PR, and it will require a lot of
> > > testing
> > > > >> due
> > > >  to the breadth of changes from dependency upgrades.  Please take a
> > > > look
> > > > >>> at
> > > >  both of these PRs.  The earlier we can get feedback, the sooner we
> > > can
> > > > >>> get
> > > >  Java 11 compatibility in an Apache NiFi release.
> > > > 
> > > >

Re: [DISCUSS] NiFi and Java 11

2019-04-04 Thread Matt Gilman 
Jeff,

I think this is a great approach that should help us transition to and in
the long run, adopt Java 11. The staggered approach should allow us to
address concerns and any issues we may encounter as we go over time.

Thanks for putting these together!

Matt

On Thu, Apr 4, 2019 at 2:19 AM Jeff  wrote:

> I created a JIRA [1] to track the developer documentation changes.  Andy,
> thanks for pointing out the specific links; I've added them to the JIRA.
>
> [1] https://issues.apache.org/jira/browse/NIFI-6187
>
> On Wed, Apr 3, 2019 at 11:23 PM Sivaprasanna 
> wrote:
>
> > Yep. Adding to GitHub template is a great idea.
> >
> > On Thu, 4 Apr 2019 at 5:27 AM, Andy LoPresto 
> wrote:
> >
> > > We should add that to the Developer Guide [1], Contributor Guide [2],
> > note
> > > it in the Migration Guide [3] when it takes effect, and include it in
> the
> > > GitHub PR template as well.
> > >
> > > [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html <
> > > https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html>
> > > [2] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
> <
> > > https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide>
> > > [3]
> https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
> > <
> > > https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance>
> > >
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > alopresto.apa...@gmail.com
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > > > On Apr 3, 2019, at 1:16 PM, Sivaprasanna 
> > > wrote:
> > > >
> > > > Sounds good to me.
> > > >
> > > > So contributors who bring in new changes are expected to write the
> code
> > > > that should be compatible with both Java 8 as well as Java 11, right?
> > > >
> > > > Do we see anything that we should have in our site that would help
> the
> > > > contributors/users with this change? Something like a document that
> > > > explains best practices which a developer should follow so that the
> > > change
> > > > which the developer is bringing in should run fine in both 8 and 11.
> > > >
> > > > -
> > > > Sivaprasanna
> > > >
> > > > On Thu, 4 Apr 2019 at 12:18 AM, Pierre Villard <
> > > pierre.villard...@gmail.com>
> > > > wrote:
> > > >
> > > >> Sounds good to me as well. Given the latest news on Java 8, having
> > the 2
> > > >> PRs merged in would be great!
> > > >>
> > > >> Thanks,
> > > >> Pierre
> > > >>
> > > >> Le mer. 3 avr. 2019 à 20:34, Joe Witt  a écrit
> :
> > > >>
> > > >>> Jeff
> > > >>>
> > > >>> This seems very reasonable and thorough to me.
> > > >>>
> > > >>> The only short term implication that we'd have to buy into then is
> > that
> > > >> PRs
> > > >>> going forward need to be able to build on both Java 8 and 11 which
> > > seems
> > > >> a
> > > >>> very fair way to bridge toward moving to Java 11 as the base
> > > requirement
> > > >> in
> > > >>> the next major release of NiFi (2.x).
> > > >>>
> > > >>> Thanks
> > > >>> Joe
> > > >>>
> > > >>> On Wed, Apr 3, 2019 at 2:19 PM Jeff  wrote:
> > > >>>
> > >  I'm reaching out to the community today to propose a plan for
> moving
> > >  forward with NiFi on Java 11.
> > > 
> > >  There are currently two PRs that deal with Java 11 compatibility.
> > The
> > >  first PR allows NiFi built on Java 8 to be run on Java 11 [1].
> The
> > > >>> second
> > >  PR allows NiFi to be built on Java 11 and run on Java 11 [2].
> There
> > > >> are
> > > >>> a
> > >  lot of changes in the second PR, and it will require a lot of
> > testing
> > > >> due
> > >  to the breadth of changes from dependency upgrades.  Please take a
> > > look
> > > >>> at
> > >  both of these PRs.  The earlier we can get feedback, the sooner we
> > can
> > > >>> get
> > >  Java 11 compatibility in an Apache NiFi release.
> > > 
> > >  I would to discuss with the community the following plan for
> > upcoming
> > > >>> NiFi
> > >  releases as they pertain to Java 11:
> > > 
> > >  For the 1.x release line, from either 1.10 or 1.11 (depending on
> > when
> > > >>> these
> > >  two PRs are merged to master) and onward, NiFi will be compatible
> > with
> > > >>> both
> > >  Java 8 and 11 for building and running NiFi:
> > > 
> > >    - Build on Java 8, run on Java 8
> > >    - Build on Java 8, run on Java 11
> > >    - Build on Java 11, run on Java 11
> > > 
> > >  The 1.x release line will contain convenience builds for Java 8,
> and
> > > >> will
> > >  NOT contain convenience builds created from Java 11.  Users that
> > want
> > > >> to
> > >  run NiFi 1.1x.y on Java 11 with Java 11 bytecode will have to
> build
> > > >> from
> > >  the released source code.
> > > 
> > >  Once the Java 11 compatibility features [1] [2] are merged to
> > master,
> > > >> PR
> > >  reviews will require building and testing with Java 8 and Java 11
> > > >> before

NiFi Boot Error

2019-04-04 Thread Bimal Mehta 
I recently upgraded to NiFi 1.9.0.
However on starting the NiFi service I get the following error

A blank sensitive properties key was provided
Specify a unique key in nifi.properties for nifi.sensitive.props.key

I am not sure about this property. What do I need to do?

Thanks
Bimal Mehta

Apache NiFi 1.9.2 RC2 Release Helper Guide

2019-04-04 Thread Joe Witt 
Hello Apache NiFi community,

Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.

Please note you might think "Hey where was RC1".  That RC failed before I
even got the vote out but I did have the tags pushed.

# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS

# Import keys file:
gpg --import KEYS

# [optional] Clear out local maven artifact repository

# Pull down nifi-1.9.2 source release artifacts for review:

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.2-rc2/nifi-1.9.2-source-release.zip
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.2-rc2/nifi-1.9.2-source-release.zip.asc
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.2-rc2/nifi-1.9.2-source-release.zip.sha256
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.2-rc2/nifi-1.9.2-source-release.zip.sha512

# Verify the signature
gpg --verify nifi-1.9.2-source-release.zip.asc

# Verify the hashes (sha256, sha512) match the source and what was provided
in the vote email thread
shasum -a 256 nifi-1.9.2-source-release.zip
shasum -a 512 nifi-1.9.2-source-release.zip

# Unzip nifi-1.9.2-source-release.zip

# Verify the build works including release audit tool (RAT) checks
cd nifi-1.9.2
mvn clean install -Pcontrib-check,include-grpc

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.

Thank you for your time and effort to validate the release!

Re: Pull Request for NIFI-1693

2019-04-04 Thread Joe Witt 
Ryan,

I recommend using the dev list exclusively instead of adding direct e-mails
as well.

In looking briefly at the PR I recommend removing changes not directly
related to the PR/discussion itself.  There are a ton of changes for
assertFalse to Assert.assertFalse for instance.  This creates a lot more to
look at and might discourage focusing on the core of your change.

Thanks

On Thu, Apr 4, 2019 at 11:33 AM Ryan Withers  wrote:

> To whom it may concern,
>
>   I put up a draft pull request based on a suggestion from Brian Bende on a
> very minor update to nifi. The pull request is here:
> https://github.com/apache/nifi/pull/3388.  It is related to this JIRA
> ticket https://issues.apache.org/jira/browse/NIFI-1693.  I still have a
> bit
> more left to do but a friend of mine suggested getting feedback before
> completing the story if it affects a large number of locations within the
> codebase.
>
>   This happens to be a relatively simple change that needs to be made in
> many different locations.  This story was one of two recommended by Andy
> Lopresto as a good place to get started.  I may have an alternative
> approach that would avoid a lot of areas of implementation (perhaps even
> centralizing it) but require all the tests and I may attempt that as a
> refactor once I've completed the changes and required tests.
>
> I'm very interested in any feedback and guidance the community may have.
>
> Thanks in advance,
>
> Ryan
>
> --
> Ryan Withers
> Senior Software Developer / Analyst
>
> http://www.linkedin.com/in/ryanwithers
>

Pull Request for NIFI-1693

2019-04-04 Thread Ryan Withers 
To whom it may concern,

  I put up a draft pull request based on a suggestion from Brian Bende on a
very minor update to nifi. The pull request is here:
https://github.com/apache/nifi/pull/3388.  It is related to this JIRA
ticket https://issues.apache.org/jira/browse/NIFI-1693.  I still have a bit
more left to do but a friend of mine suggested getting feedback before
completing the story if it affects a large number of locations within the
codebase.

  This happens to be a relatively simple change that needs to be made in
many different locations.  This story was one of two recommended by Andy
Lopresto as a good place to get started.  I may have an alternative
approach that would avoid a lot of areas of implementation (perhaps even
centralizing it) but require all the tests and I may attempt that as a
refactor once I've completed the changes and required tests.

I'm very interested in any feedback and guidance the community may have.

Thanks in advance,

Ryan

-- 
Ryan Withers
Senior Software Developer / Analyst

http://www.linkedin.com/in/ryanwithers

Re: [DISCUSS] NiFi and Java 11

2019-04-04 Thread Jeff 
I created a JIRA [1] to track the developer documentation changes.  Andy,
thanks for pointing out the specific links; I've added them to the JIRA.

[1] https://issues.apache.org/jira/browse/NIFI-6187

On Wed, Apr 3, 2019 at 11:23 PM Sivaprasanna 
wrote:

> Yep. Adding to GitHub template is a great idea.
>
> On Thu, 4 Apr 2019 at 5:27 AM, Andy LoPresto  wrote:
>
> > We should add that to the Developer Guide [1], Contributor Guide [2],
> note
> > it in the Migration Guide [3] when it takes effect, and include it in the
> > GitHub PR template as well.
> >
> > [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html <
> > https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html>
> > [2] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide <
> > https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide>
> > [3] https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
> <
> > https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance>
> >
> >
> > Andy LoPresto
> > alopre...@apache.org
> > alopresto.apa...@gmail.com
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > > On Apr 3, 2019, at 1:16 PM, Sivaprasanna 
> > wrote:
> > >
> > > Sounds good to me.
> > >
> > > So contributors who bring in new changes are expected to write the code
> > > that should be compatible with both Java 8 as well as Java 11, right?
> > >
> > > Do we see anything that we should have in our site that would help the
> > > contributors/users with this change? Something like a document that
> > > explains best practices which a developer should follow so that the
> > change
> > > which the developer is bringing in should run fine in both 8 and 11.
> > >
> > > -
> > > Sivaprasanna
> > >
> > > On Thu, 4 Apr 2019 at 12:18 AM, Pierre Villard <
> > pierre.villard...@gmail.com>
> > > wrote:
> > >
> > >> Sounds good to me as well. Given the latest news on Java 8, having
> the 2
> > >> PRs merged in would be great!
> > >>
> > >> Thanks,
> > >> Pierre
> > >>
> > >> Le mer. 3 avr. 2019 à 20:34, Joe Witt  a écrit :
> > >>
> > >>> Jeff
> > >>>
> > >>> This seems very reasonable and thorough to me.
> > >>>
> > >>> The only short term implication that we'd have to buy into then is
> that
> > >> PRs
> > >>> going forward need to be able to build on both Java 8 and 11 which
> > seems
> > >> a
> > >>> very fair way to bridge toward moving to Java 11 as the base
> > requirement
> > >> in
> > >>> the next major release of NiFi (2.x).
> > >>>
> > >>> Thanks
> > >>> Joe
> > >>>
> > >>> On Wed, Apr 3, 2019 at 2:19 PM Jeff  wrote:
> > >>>
> >  I'm reaching out to the community today to propose a plan for moving
> >  forward with NiFi on Java 11.
> > 
> >  There are currently two PRs that deal with Java 11 compatibility.
> The
> >  first PR allows NiFi built on Java 8 to be run on Java 11 [1].  The
> > >>> second
> >  PR allows NiFi to be built on Java 11 and run on Java 11 [2].  There
> > >> are
> > >>> a
> >  lot of changes in the second PR, and it will require a lot of
> testing
> > >> due
> >  to the breadth of changes from dependency upgrades.  Please take a
> > look
> > >>> at
> >  both of these PRs.  The earlier we can get feedback, the sooner we
> can
> > >>> get
> >  Java 11 compatibility in an Apache NiFi release.
> > 
> >  I would to discuss with the community the following plan for
> upcoming
> > >>> NiFi
> >  releases as they pertain to Java 11:
> > 
> >  For the 1.x release line, from either 1.10 or 1.11 (depending on
> when
> > >>> these
> >  two PRs are merged to master) and onward, NiFi will be compatible
> with
> > >>> both
> >  Java 8 and 11 for building and running NiFi:
> > 
> >    - Build on Java 8, run on Java 8
> >    - Build on Java 8, run on Java 11
> >    - Build on Java 11, run on Java 11
> > 
> >  The 1.x release line will contain convenience builds for Java 8, and
> > >> will
> >  NOT contain convenience builds created from Java 11.  Users that
> want
> > >> to
> >  run NiFi 1.1x.y on Java 11 with Java 11 bytecode will have to build
> > >> from
> >  the released source code.
> > 
> >  Once the Java 11 compatibility features [1] [2] are merged to
> master,
> > >> PR
> >  reviews will require building and testing with Java 8 and Java 11
> > >> before
> >  the PR is merged to master. We will add a new build to our Travis CI
> >  instance to cover building on Java 11, which should help with the PR
> >  process, since build status from Appveyor and Travis are shown on
> the
> > >> PR.
> >  This will allow an easier transition to the NiFi 2.x release line.
> > 
> >  For the 2.x release line, the minimum Java version would be Java 11,
> > at
> >  which point developers would be able to start using Java 11 language
> >  features.  Java 12 is not designated to be an LTS release, with its
> > >>> support
> >