Re: [PHP-DEV] Bug fixing and CVS
On Fri, 7 Mar 2003, Jean-Michel Dault wrote: I maintain PHP for Mandrake Linux, and I try to ship a bug-free PHP. bug-free doesn't exist :) That is, if there were some showstopper bugs that were not corrected in 4.3.1, I take the bugfixes from CVS and apply them. If you want to do that, then just use the latest stable CVS snapshot... My concern is: php-bugs always says This bug is fixed in CVS, then I have to look through php-cvs and try to find what changes were made concerning that specific bug. Is there a better way? Is there a special CVS command to show the diffs on a changelog entry? Nope, there is no command for that. Would something like bugs.php.net/patches with a list of all closed bugs and their corresponding diffs be thinkable? It wont be practicle... it means another extra step for the devs and it will sometimes be forgotten... I don't think it's a good idea as you can always see the CVS commits on the php-cvs@ list anyway. Derick -- my other box is your windows PC - Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Bug fixing and CVS
Le sam 08/03/2003 à 10:31, Derick Rethans a écrit : I maintain PHP for Mandrake Linux, and I try to ship a bug-free PHP. bug-free doesn't exist :) I said I try ;-) I always try the impossible ;-) That is, if there were some showstopper bugs that were not corrected in 4.3.1, I take the bugfixes from CVS and apply them. If you want to do that, then just use the latest stable CVS snapshot... I would, but the problem is that the snaps are always updated, and the old files deleted, and my QA requires that the sources be always available at the same URL. Hmmm.. are they really deleted, or it's just that the snaps.php.net only shows the recent files? Also, right now Mandrake is in deep freeze, so I can only add new patches if they are fully documented and tested. I just can't diff the cvs with the standard version and apply the changes, otherwise the package won't be accepted. Is there a better way? Is there a special CVS command to show the diffs on a changelog entry? Nope, there is no command for that. That's what I thought, but I wasn't sure. Would something like bugs.php.net/patches with a list of all closed bugs and their corresponding diffs be thinkable? It wont be practicle... it means another extra step for the devs and it will sometimes be forgotten... I don't think it's a good idea as you can always see the CVS commits on the php-cvs@ list anyway. I understand perfectly. One last question: is a .phpt file created for every closed bug report, or is it something that only a couple of developers do? Thanks for taking the time to reply to my (silly?) questions, and specially for the prompt replies. =) When you come to Montreal, the beer is on me ;-) Jean-Michel -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Bug fixing and CVS
I would, but the problem is that the snaps are always updated, and the The constant names are php4-latest.tar.bz2 php4-STABLE-latest.tar.bz2 php5-latest.tar.bz2 old files deleted, and my QA requires that the sources be always available at the same URL. The sources are available at the same URL all the time; however, it is not always the same source. Hmmm.. are they really deleted, or it's just that the snaps.php.net only shows the recent files? Old files are purged regularly. - Sascha -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Bug fixing and CVS
On Sat, 8 Mar 2003, Jean-Michel Dault wrote: Also, right now Mandrake is in deep freeze, so I can only add new patches if they are fully documented and tested. I just can't diff the cvs with the standard version and apply the changes, otherwise the package won't be accepted. That's not really our problem, is it? Would something like bugs.php.net/patches with a list of all closed bugs and their corresponding diffs be thinkable? It wont be practicle... it means another extra step for the devs and it will sometimes be forgotten... I don't think it's a good idea as you can always see the CVS commits on the php-cvs@ list anyway. I understand perfectly. One last question: is a .phpt file created for every closed bug report, or is it something that only a couple of developers do? It should be done by everybody, but that's unfortunately not how it is. The QA team tries to push it as much as possible though. If you find that it has not been done for a bug, please drop a note to [EMAIL PROTECTED] Thanks for taking the time to reply to my (silly?) questions, and specially for the prompt replies. =) When you come to Montreal, the beer is on me ;-) That was not a smart, as I'll be there the 19th to 21st for the PHP Quebec Conference :) Derick -- my other box is your windows PC - Derick Rethans http://derickrethans.nl/ PHP Magazine - PHP Magazine for Professionals http://php-mag.net/ - -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Bug fixing and CVS
Le sam 08/03/2003 à 12:59, Derick Rethans a écrit : Also, right now Mandrake is in deep freeze, so I can only add new patches if they are fully documented and tested. I just can't diff the cvs with the standard version and apply the changes, otherwise the package won't be accepted. That's not really our problem, is it? Nope, it's all mine =) Thanks for taking the time to reply to my (silly?) questions, and specially for the prompt replies. =) When you come to Montreal, the beer is on me ;-) That was not a smart, as I'll be there the 19th to 21st for the PHP Quebec Conference :) I know, I visit the site every day to see if Damien finally got his mail and I'm not listed twice, but I still am... The beer offer still stands, it sure won't be as expensive as the last Linux-Expo in Montreal, where I invited everyone, paid all drinks and made burgers all night. And Rasmus won't have to help me carry the food from the store ;-) Jean-Michel -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Bug fixing and CVS
Hello, I'm not sure this is the right mailing list, but at least it's not about development _with_ php, it's about development _of_ php ;-) I maintain PHP for Mandrake Linux, and I try to ship a bug-free PHP. That is, if there were some showstopper bugs that were not corrected in 4.3.1, I take the bugfixes from CVS and apply them. My concern is: php-bugs always says This bug is fixed in CVS, then I have to look through php-cvs and try to find what changes were made concerning that specific bug. Is there a better way? Is there a special CVS command to show the diffs on a changelog entry? Would something like bugs.php.net/patches with a list of all closed bugs and their corresponding diffs be thinkable? Jean-Michel -- PHP Development Mailing List http://www.php.net/ To unsubscribe, visit: http://www.php.net/unsub.php
