This way we can keep track of the underlying ABI in case a business
version needs to find its way back to community ABI.
In general ALTABI is just the derived ABI version, i.e. the one that
shares the same build settings/packages/OS version.
o Remove revoked business fingerprints that were never used
o Revoke fingerprint for 21.1 as it is no longer needed
o Remove upgrade hint file to avoid development version upgrade loops
phalcon 4 migration #4012
o replace Phalcon\Session\Adapter\Files with new Phalcon\Session\Adapter\Stream adapter
o replace router->setUriSource() with handle() parameter
o combining sessions between phalcon and legacy php seems to be a bit problematic, first issue seems to be the legacy csrf check. refactor to use phalcon's method and legacy session
o Fix Phalcon Syslog usage in ControllerRoot (wrap in Logger class)
o session seems to miss standard prefix.
o also Gettext seems to like being wrapped...
o Gettext inheritance
o another handle()
o Volt: handle registerEngines / VoltEngine changes
o volt templates - missing session reference, bootstrap in ControllerBase
o router getRewriteUri() deprecated
o another handle() in index.php
o Phalcon\Dispatcher::EXCEPTION_* moved to Phalcon\Dispatcher\Exception::EXCEPTION_*
o changes in filter handling.
o fix plist
o Syslog usage changes
o refactor Validation changes
o FILTER_ALNUM - replaced FILTER_ALPHANUM
If CORE_NEXT.b tag exists do not use anything else anymore,
otherwise if CORE_NEXT* something exists use this, otherwise
hands off from manual tag pattern matching.
Since this is based on computation of CORE_ABI input we
can use this on the development track to always figure out
the correct version to use without checking the CORE_ABI
explicitly.
Use CORE_NEXT in a file replacement as well.
We could keep syslog-ng329 or we could just dash ahead with the
same binary package now named syslog-ng. Breaks core builds
intermittently but all will be fine once 20.7.5 hits.
