On Thu May 19, 2005 at 08:5827PM +0200, Stefano F. Rausch wrote:
Not at all Martin. TestFileLoader is just a small contribution and as such it doesn't need an own category. I'm just wondering, how (has it already been done in the past?) third party contributions are being separately integrated into the main package (they obviously belong to).
If the contribution is so small, then why not bundle it directly with
PHPUnit2? If you or Sebastian don't want this, I'd suggest the
package goes directly into the "Testing" category.
- Martin
On Fri, 20 May 2005 06:51:15 +0200, Sebastian Bergmann <sb@sebastian-bergmann.de> wrote:
Stefano F. Rausch wrote:
Should I go for Testing :: PHPUnit2 ...? I have no clue.
I am unsure of whether or not to include your TestFileLoader into the
main PHPUnit2 package.
Having your own package has the advantage that you have full control
over your release cycle. If I were to integrate it into the main
PHPUnit2 package the earliest possible release that would contain your
TestFileLoader would be PHPUnit2-2.3.0 which is not going to be released
any time soon.
If you decide to maintain a separate PEAR package for your
TestFileLoader the package would be called PHPUnit2_TestFileLoader and
the category would be the same as PHPUnit2's.
I would not mind waiting for a new release of PHPUnit2 for TestFileLoader to be integrated into.
However, having said this and the fact that Sebastian is still unsure if to include my suggestion at all, I think it's legitimate to go for a PEPr and the Testing::PHPUnit2_TestFileLoader package and to see what the outcome will be. I will launch a respective PEPr after having sorted out my current ScriptReorganizer proposal ... ;-)
Thanks guys!