Re: Unit tests, was Re: [PEAR-DEV] an HTML_Template_IT[X] fork is available

> >>> We don't have to prove, that your new package breaks BC, > >>> you have to prove, that it does not! > > Not to encourage further argument, but I feel that this is an > unreasonable statement. Since there are no unit tests to verify, > nobody can prove anything is BC or not. This makes patch-work, with or > without a proper patch, and analysis of new contributions much more > difficult, and more prone to error. In turn, this creates a barrier to > entry for PEAR contributions, which is IMO a bad thing. You are right. He can't prove that his package does not break BC. I don't think, that this is a good situation. Some way to test would be really nice. The fact, that we don't know if his package breaks BC or not is a problem, especially when it comes to a widely used package which was around for a long time. And you are right: This creates a barrier! But we can't just create a hole and let all people run through it ... We need to disassemble the barrier piece by piece ... Christian Dickmann