To see the progress I am digging through the resolved issues and that list is slowly but steadily growing.

Right now there are about 7 issues left, although some might not get resolved for the next release.

One of the bigger issues is to upgrade ZenMagick to using the symfony routing component. This is not a small task and even after I thought I was finished with the component integration there was still plenty to do and improve.
Now all that is left to do is waiting for someone to donate a routing config file

So, what else is new?

• Plain object controller
  Together with the routing integration there is now support to use any given class/method as controller. That means the method can be mapped to a request and there is no restriction to the proccess method any more.
  This is in line with the way other frameworks do things and something people have been asking for quite some time
• Admin Store Status widget refactoring
  The refactored code now allows plugins and other code that has access to the service container to register custom status checker to this widget. That means all important status checks can now be in a single consistent format/place.
• bootstrap refactoring
  The files bootstrap.php and mvc.php are no longer supported and have been removed. The whole bootstrap/request handling process has been replaced by the zenmagick\base\Application and zenmagick\http\WebApplication classes.
  This also allows to bootstrap individual components only, bootstrap without an application and more.
• POMO
  ZenMagick is now using .po files for translations, just like WordPress (in fact it uses the same code for handing .po and .mo files). Applications, themes and plugin now can contain translation files that will be merged during bootstrap.
• doctrine
  Doctrine integration is progressing with some issues remaining that might only get fixed once we allow ZenMagick to control the request entirely, rather than run as a subsystem of zencart.

Some of the above changes have had widespread impact on the codebase, so upgrading has do be done with care.

In addition there is the ongoing work to migrate code to namespaces and generally improve the code (while doing that).

Next on the list of things are (in no particular order):

• Validation
  It would be nice to move to the symfony validation code, but first there has to be support for client side (JavaScript) validation. There has been a jquery plugin for the old symfony code, but so far nothing for sf2.
• Installer
  There  is an (empty) store-installer application now in the repository. Not sure if there is enough time to get this going for the next release, but things are moving forward.
• Upgrade
  Paving the way for the stand alone installer is a new upgrade option. This will replace the current installation page and hopefully be even simpler.

I am sure there has been more, but the above seem to be the bigger tickets.