separate releases of 4.X and 5.X

[mckaygerhard]

This is because it seems that the project itself will evolve so much that it will not be possible to have a "single file database manager" as final product... it will become a multi-file project in the releases... even a "single file database manager"

So i propose the separation:

1. git Branch Release series 5.X will be not a single file, the frontend, the editor, the plugins and the themes with docs etc etc I already check the git branch and this is a inevitable future.. also will remove the php older support too so many rare combinations will sufers from, all new features will go only to this branch like the reported at Undefined property: stdClass::$table in adminer.php on line 1523  adminerevo/adminerevo#116
2. git branch release series 4.X as "single file database manager" with less features... just the curent support for ALL databases olders and newers.. but without large features.. (noted in some issues about newer features inside DBMS) only receiving updates for fixes or database support, but not new features more far from suport variations (like the new mariadb vs mysql separation).

[peterpp]

Release series 5.X will be not a single file

Not true. Single file version is the core feature and version 5 will keep it and even improve it. I plan to add support to compile also selected plugins and themes into a single file.

also will remove the php older support

True. Support for very old PHP versions could be kept, but the effort is just too big. New language features allow us to make the code more readable, robust and safe.

series 4.X with less features

I know there is still a demand for PHP 5. I'm not strictly rejecting some kind of backporting to version 4, especially bug fixes. But I don't want to make any promises right now. We will see how it evolves.

[mckaygerhard]

I know there is still a demand for PHP 5. I'm not strictly rejecting some kind of backporting to version 4, especially bug fixes. But I don't want to make any promises right now. We will see how it evolves.

the separation proposed help both sides.. you can focus on newer ways adn the other peoples can contribute to olders ways.. but well..

the problem is that fashion trends are often confused with what security really is.. you arged readable code but many people just need more spatial and abstrac understanding.. so collaboration is often not so easy due that..

but as developer i vaticine your response.. developers just like complicated things and talks about standarts and integrations..

[peterpp]

I am closing this issue because it is more like discussion topic.