Re: Automatic changelog display?

On Friday, September 19, 2003 17:58, Greg Beaver wrote: > Tomas V.V.Cox wrote: >>You just need to go to the package home for getting this info, both >>the changelog and the bugs. The PEAR installer TODO list has grow >>enough for a year of working, including: PECL binaries, channels, >>subpackages, api generation, dtd validation, applications, among >>others, so please don't ask and ask for stuff but help (or well put >>some funds ;). >> > We don't need money, we need people willing to do unit testing and > documentation for current features :). I can't work any faster if I am > paid - it's not like the extra time exists. In my case as freelance I do can, others may be in the same situation, but was just kidding nm. > PEAR_Common, for instance, has tons of critically important stuff which > works in most cases, but might not work in all since the inputs are not > validated - you can't have a program that is guaranteed to work unless > you guarantee that all the inputs will be within a finite set and that > it generates the correct output from that set, but this is all old > theoretical hat. Oh finallly you know why I'm coding XML_DTD :-) > I'm still waiting for a response on the need for a test server to unit > test the download methods of PEAR_Installer. I can't go any further > unit-testing that area unless there is an official test server set up > which can be used to test the download methods. This server should be > hosted through php.net, in my opinion, even if it is a virtual redirect > to another host. As Martin pointed out, there is room in pear.php.net. But I'd recommend you to install the pearweb locally, is not that hard, I could help you there. This way is from far faster than using a remote site where updates takes ages :-) > Josh Eichorn has mentioned to me that he would be happy to host the test > server on his site, perhaps that is an option (test.pear.php.net maybe?) Thanks Joshua, -- Tomas V.V.Cox mailto:cox@idecnet.com