Jonathan Asghar wrote:
I have to agree with Johannes here, the testing should happen on the dev side and there should be some type of "QOS" control for a port that we produce.
this implies that $ARCH developers should test every known port of core/opt (and contrib?) collections... and it is not acceptable for me, specially for little communities, infact it produces two negaive aspects for the 90% of ports: 1. $ARCH dev are really overloaded 2. $ARCH ports can remains outdated for a long period and the only 1 positive effective for the remanent 10% of buggy ports: 1. port usable without sending a ticket to the $ARCH developers consider also the "obviously tested" ports distributed on the $ARCH iso image regards -- Giulivo Navigante http://cruxppc.sunsite.dk