PEAR_PackageUpdate 1.1.0 roadmap

Hello all, While I've begun to work on new version 1.1.0 of PEAR_PackageUpdate (to add new features), I've found a bug. Just in case you got a problem with release 1.0.0 and setMinimumReleaseType() method using constant PEAR_PACKAGEUPDATE_TYPE_MINOR, it's a real bug ! I just found it : there is a typo error at line 1044 of v1.27

1044:          && $minType != PEAR_PACKAGEUPDATE_TYPE_MINOR²

-------------------------------------------------------------------------------^ I've fixed it in CVS (see new revision 1.31) New release 1.1.0 is planned for June 1st. If you can't wait , you just have to remove the "²" character at end of line , or get the revision 1.3.1 in PEAR CVS Now here are the new features for new API 1.1.0 : - ability to choose protocol to contact server (default is 'auto', try first REST 1.0 then RPC) that means you may decide to contact a channel server only with RPC or even with REST 1.1 (1.2, 1.3) if supported - ability to choose what mirror to contact without changing pear config - add event driven possibility with help of package Event_Dispatcher - add report in multiple formats (template, xml, ...) about last package update If you have another idea, that you want to see in this package, don't hesitate to post a request on PEAR bugtracker. Regards Laurent Laville