Download
2012-03-08, 07:45:58
On the plugins issue, one more comment. Another possibility (that I was thinking to suggest for 3.2) is doing like WP: plugins must be activated in the backend, or else they're not loaded in the frontend.
It would simplify this: the plugins.xml file would only be rewritten when in admin>plugins.
Another suggestion: copy 3.1.x to another branch in the svn. The current branch would be now 3.2 beta.
If some -important- new issue is found later, you do the fix in both and release a 3.1.(x+1) for easy upgrade.
This separation would better be done when current known issues are fixed, so that you don't have to do double work for the svn.
(I imagine that mantaining 2 versions is too much work for this small dev team, that's why I haven't suggested this before.)
It would simplify this: the plugins.xml file would only be rewritten when in admin>plugins.
ccagle8 Wrote:Also, just so you guys know, the 3.2 or 4.0 (whichever is may be) roadmap will start being discussed shortlyI suggest you release 3.1.1, 3.1.2, ... to fix all known issues (including the menu manager) before starting with 3.2.
Another suggestion: copy 3.1.x to another branch in the svn. The current branch would be now 3.2 beta.
If some -important- new issue is found later, you do the fix in both and release a 3.1.(x+1) for easy upgrade.
This separation would better be done when current known issues are fixed, so that you don't have to do double work for the svn.
(I imagine that mantaining 2 versions is too much work for this small dev team, that's why I haven't suggested this before.)
