Re: Proper patch and bug handling
| From: | Wolfram Kriesing | Date: | Sat, 05 Jul 2003 16:52:07 +0000 |
| Subject: | Re: Proper patch and bug handling | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-18031@lists.php.net to get a copy of this message | ||
Martin Jansen wrote:
On Sat Jul 05, 2003 at 03:1648PM +0200, Mirco 'meebey' Bauer wrote:does the problem need to be solved or do we need to fulfill some unwritten rule? If the second thing is the case i think focus is lost ... but if that's what you need to do ... I think all the arguments to use already written software and not reinvent the wheel are not necessary to be mentioned here, since everyone knows them ... pear is opensource and is meant to be used by other, so why would vice versa not work too? -- Wolfram http://opensource.visionp.de ... authentication system .... http://sf.net/projects/authhhhm which tracker will be used then? It would be good if the tracker can handle patches (uploading files) and bugs (for later purpose) At work we use phpBugTracker and it does a great job, but it does not have any patch tracking...The (unwritten) rule for pear.php.net is to use third-party code only when it's absolutely necessary. Thus we will have a home-brewed system for tracking patches, which will offer an API where the upcoming bug reporting interface can hook in.