|
From: Perrick P. <pe...@no...> - 2009-02-09 09:40:43
|
Hi, >> I haven't seen it in /trunk yet. I think it's still in its own branch. >> Maybe we can port it to trunk now ? What do you think ?? > > If it's easy to use and works, then it should go in. We won't announce > it, but it should be in there. It's in now (the code coverage stuff). > I'll leave the final choices up to you though. My main job (once I've > moved house in two weeks) is to finish the core documentation. It makes > sense for you to take on the role of buildmeister for a little bit (if > you are willing?). And I finally have some time. We moved house in december as well ;-) And No Parking (my company) will change offices soon as well. On our TODO master plan, there are 2 items left before we can release : 1/ an old bug [ 1896582 ] Undefined property $_reporter + fatal error http://sourceforge.net/tracker/index.php?func=detail&group_id=76550&atid=547455&aid=1896582 2/ Update PEAR package task to be compatible with latest PEAR installer. For item 1/, I think the author solved it in his code ("Figured it out."). So I feel we can drop the report now ;-) For item 2/, we still need someone to pick up the task. If noboby is up for it, I feel we can postpone this feature. I feel that getting some feedback on the code coverage stuff is a lot more crucial. By the way, I'd love to have some documentation on "how to code-coverage my code". Douglas : would you be kind enough to add something in the docs/source/en directory ? The XML format we use should be trivial enough to figure out and use. Anyway, I hope we can release 1.1beta by the end of this month (that's my target anyway). Yours, Perrick |