Making workflow to naturaly autobalance

It is suggested considering not focusing in the engineers workflow but simplifying and making to naturaly balance the project's workflow itself, by taking into account some of these approaches:

- Asking users to overlook their bugs, for deleting old ones
- Making debian-testing the base imported repository from Debian, and debian-unstable the one which completes any critical package not provided in the first
- Redesigning packages version updating for automaticaly not to let so buggy features to enter the end-user repository
- Making applications based in an auto-generated rolling release update scheme, but keeping libraries and core system in a regular schedule but with a larger circle
- Eliminating the LTS release, and providing support and bug solving only for the last two versions of the system

So:

- The base system is stable and with a predictable development
- Applications are the most modern they can be without being buggy
- The workflow don't need engineer attention further than its design

- Large deployments can use the standard edition, since major updates are only needed after much time
- Not needing of debugging for so many different editions of the operating system