making stuff a reality
| From: | Lukas Smith | Date: | Wed, 21 May 2003 10:23:45 +0000 |
| Subject: | making stuff a reality | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-16562@lists.php.net to get a copy of this message | ||
Hi,
as you can see from the meeting summary there are a bunch of todos that
come of it. I might have missed some things. Anyways please speak up if
you want to take on a certain part. The Qa team is already forming.
1. Forming of a QA team
* Defining methods to ensure our quality standards
2. Some more research regarding phpt vs. phpUnit
* Advantages of each framework
* Possible improvements
3. deprecated packages.
* Creation of an archive zone for deprecated pear und pecl packages
4. Method Naming Conventions suggestions for the PEAR Group
5. Forming of a Doc Team
* write tutorials on how to write documentation
* provide tools to make doc generation easy since Docbook is currently
the standard format.
* ensure that this generation does not need any non-standard tool or
services on pear.php.net to be made available so that people don't need
so install this software locally.
6. Forming of a PEAR group
* coming up with regulations to handle itself
* set standards (like method naming conventions)
7. PEAR Website
* add votes and comments for packages
* Proposals and voting
8. Installer
* improve the version handling, we especially need to add a guide on
version naming in the PEAR manual.
* PECL installer does not work on Windows
* PECL installer does not detect if an extension is loaded while
upgrading it that creates a possible crash.
* Need to check in the packager to verify if the version name is
correct (that will be registered as an upgrade)
* Need binaries handling for different platforms
* updating stables should not be updated with lower "level" (beta,
alpha) releases
* BC breaking releases should not be done automatically (i.e.
upgrade-all)
* Installation of older versions should not require the complete URL but
only by adding the version number
9. Installer Future plans:
* mirror support
* automatic dependency resolving through a local database
* move away from xml-rpc
* taking another look at an rpm based solution
10. PHP5
* Define what we need in PHP5
* Define how maintaining PHP4 and PHP5 will be done