PNDA releases up to PNDA 5.0 were deployed using Saltstack from a pre-built mirror of RPM, Python, NPM, Hadoop and 3rd party packages. A release built for a version of Centos, e.g. 7.5-1804, will typically break for a new Centos release, e.g. 7.6-1810. Likewise, change in the Python or NPM package repositories can also break the PNDA release. This results in a maintenance burden on project contributors, just to keep PNDA releases working. A significant proportion of discussion on the mailing lists is helping people to resolve this release fall-out.
The PNDA contributors are currently working on a Cloud-native PNDA that uses Helm and Kubernetes to deploy and manage containerised PNDA components. This ensures that dependencies will get resolved at build time and container images will provide the necessary isolation at deployment/run time.
There are currently only a few active PNDA contributors making changes on a best-effort basis so it is not realistic to plan a date for the next PNDA release. It will be released when it is usable enough to be useful.
Once we have a first Cloud-native release of PNDA, it is realistic to aim for a modest release cadence such as 3 or 4 releases per year. This would allow for new features to be developed and delivered along with existing PNDA components that could remain unchanged. It would also allow for us to be responsive to security vulnerabilities and upstream changes on a per PNDA component basis, rather than for a monolithic release.