As said by others, there does need to be a reason for PHP5 change. Is
there any proposed code that requires PHP5, probably not.
My vision would be that RC changes to PHP5 in a major release eg.
Roundcube 2.
There would be little point swapping to PHP5 without re-doing classes
using the new OOP features, implementing exception catching etc. (taking
advantage of it).
Also a coding guide should be developed to advise devs of the minimum reqs
to fulfill.
I see this as a separate project for the project in the future. People are
going to need PHP4 support still for some time to support legacy webapps
and also because of slack admins.
rgs,
Chris
On Tue, 19 Jun 2007 09:23:42 +1000, Brian Jackson <[EMAIL PROTECTED]> wrote:
I haven't so far because I didn't have a good solution for the older db
library other than just say forget it. I didn't think that would go over
very well, but if mdb2 becomes the only db library, I'd be more than
happy to resurrect the patch and port it to latest svn. I may have even
had at one point a patch to rip out the older db library and leave all
the db access parts connected directly to mdb2, but I'd have to dig a
lot for that.
--Brian Jackson
On Jun 18, 2007, at 5:11 PM, till wrote:
On 6/18/07, Brian Jackson <[EMAIL PROTECTED]> wrote:
If roundcube did switch to requiring mdb2, I have a local patch that
uses mdb2's xml schema stuff to automatically install and maintain
the database table layout.
Very cool, maybe you want to open a ticket on the trac?
Cheers,
Till
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
