Re: PHP 4.0.5 Release & Midgard Problems

> > PHP and midgard is still undergoing heavy development. Actually it's stable release went out a few days ago? - the midgard team actually aimed at matching the PHP release cycle.. - all modifications at present are pure bug fixes.. > > > > Sascha complains about the stability of PHP and all of our patch levels yet > > Rasmus wants to include these extensions that are applications in their own > > right, it just isn't practical for the QA team to test something the size of > > midgard and thus it doesn't get tested (unless the midgard folks test it > > which we have to presume doesn't happen as we get no feedback from them), we > > then risk getting to a point like this where we are about to release PHP > > 4.0.5 and it either 1) has to be delayed with another release cycle 2) has > > to continue with a broken midgarad, neither are great but for the QA team > > its very annoying when midgard, somewhat of an outside extension means we > > have to do a whole new cycle. We are one of the bigger application developers on midgard (having done nadmin http://www.hklc.com/midgard_manual), and also probably the bigger bug finder & fixer - Midgard bugs are reported and fixed on it's own mailing list - outside of php-dev. (considering the traffic here - It helps everybody...) In terms classing midgard as an extension, it seems that it is no difference in terms of maintenance (QA etc.) to other extensions like ming, xml ... (great work there too..) the whole extenstion scheme works very well, however the line between 'core extension' and 'other extension', has and probably will continue to be vague. Interestingly, Our test builds of midgard are always done against packaged systems (arvins work on rpms - many kudos there). As the generally we need to install midgard into production enviroments. So it has been important to have midgard compile against earlier versions of PHP4 - from what we saw, the backwards compatibility issue has caused a few problems as the API in PHP4 gets modified slightly so it breaks this compatibility. I would urge the PHP development team to support midgard module (just by keeping it the core dist. under ext.) > > If I'm not mistaken, the midgaurd extension itself, only provides > functionality to the "midguard" application? Ie, end-users of midguard > will not use the functions and classes exported by the extension, only > midguard will use that functionality? Isnt that a bit like saying the XML module only provides functionallity to a XML application.. end users - use the midgard functions - we have almost completed a port of openmerchant to PHP4/midgard - it stores the templates and some trasent data in midgard datastore, along with the page's - it adds a level of security, reducing or removing the dependance of file system write access. Regards Alan Knowles P.S. Anybody fancy looking at the chinese htmlcharacters bug + patch :) > If so, I'm not too sure it would be a good idea to include the midguard > extension in PEAR either... > > -Sterling > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net