Define roadmap for next version

[PeeHaa]

Setup a roadmap for features for the next major version (2.0)

[PeeHaa]

While I make my mind up what I will put in the next major version and where to communicate it I will post the WIP roadmap here for the next major version:

• Finish integration of the APCu branch
• Implement memcache GUI
• Split up the firewall and authentication so both can be enabled / disabled separately
• Implement ability to implement different users (with native "jailing" and possible manual fallback)
• Implement adapter for authentication and possibly the firewall so that it can be fed using e.g. a database (useful for e.g. ISPs)
• Look into feasibility of implementing a way to invalidate an entire directory
• Look into feasibility of implementing a way to warm up the cache using a list of files / directories.
• Look into feasibility of implementing a way to manage different servers centrally (useful for e.g. ISPs) (Ability to connect to multiple php5-fpm backend servers  #60)
• Move Autoloading To Composer
• Split up the project into reusable components
• Create an installation page on fresh installs
• Create an update/upgrade page for existing installs
• Add support for IPv6 addresses. The ipv6 loopback address can be released under a patch version in the mean time.
• Use proper ISO codes for translation files

This list is no guarantee that features will actually be implemented or even looked at (but most likely will) at least until this roadmap is not a work in progress anymore.

[robfrawley]

#52