In general everything is going according to the plan with minor deviations. Currently we're actively working on both branches 2.x and 3.x. Let's get into details for each branch.
Limb 3.x
1) Packages deployment and interaction schema is almost complete. Currently it depends on using __autoload and ClassMap for class code inclusion. Packages directories are found automatically via LIMB_PKG_INCLUDE_PATH or can be defined explicitly via LPKG_xxx_DIR constants. "Almost complete" means we're not 100% sure whether enforcing the end user to use __autoload is a good thing. Another problem is code obscurity - it's unclear what package a class is actually included from. Well some reasonable class prefixes may help, e.g. class coming from core package must contain 'core' word in its name but it's quite ugly.
The only way to see downsides of this schema is to put it to practice. However we have some ideas on how to use nice __autoload stuff much less obtrusive way and make classes inclusion more explicit(this topic deserves its own thread).
2) It's still unclear when namespace support will be available in PHP and because of possible class names collisions it makes sense to give all classes some reasonable short prefix, e.g. 'lmb'. Any better ideas on prefix? Care to share?
3) 'core' package is subject to further splitting into more specialized packages like 'filter_chain', 'proxy', 'di', 'test', 'cli' etc. Still we need some time to see the advantage of such splitting before doing so.
4) We're currently working on several projects based on 3.x packages(mostly 'core' and 'cms'). It's these real projects which should show us drawbacks and missing functionality of the whole system early. Code generation tools based on meta information allowing to build application skeleton are especially in need and we're working actively in this direction.
Once we have these experimental projects finished we'll set ourselves to launching the Limb PEAR channel with subsequent release of the main packages.
Limb 2.x
Mostly bug fixes and minor changes are made in this branch. We don't want to dive too much into further development of the 2.x version, since 3.x 'cms' package should completely replace the 2.x while preserving all good stuff from it. Maintaining both code bases is getting more and more tedios every day.
Within several days there should be 2.4-alpha3 release rolled out(mostly a bug fix version).
