#18807 [Opn]: Please quote likely version number in "fixed in CVS" message
| From: | tal@php.net | Date: | Thu, 08 Aug 2002 15:58:35 +0000 |
| Subject: | #18807 [Opn]: Please quote likely version number in "fixed in CVS" message | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-16296@lists.php.net to get a copy of this message | ||
ID: 18807
Updated by: tal@php.net
Reported By: m.ford@lmu.ac.uk
Status: Open
Bug Type: Feature/Change Request
Operating System: n/a
PHP Version: 4.2.2
New Comment:
I can see your point, but there is a problem. We always fight about the
next version number :-)
So, maybe just add a note that the fix will only appear in the next
released version?
-Tal
Previous Comments:
------------------------------------------------------------------------
[2002-08-08 11:28:29] m.ford@lmu.ac.uk
A lot of work has been done in improving the standard response message
in the bug system, and they're now much better -- thanks.
But there's still an obvious problem with the "fixed in CVS" one, as
evidenced by the number of people beating you up about "fixed in CVS"
bugs that aren't fixed in 4.2.2! It would be very helpful if you
could always quote the anticipated version number when saying "fixed".
(This would also help when searching the database, as it would be clear
whether a "fixed" bug is actually fixed in the version in use.)
A second issue here is use of the term CVS, as it often seems to be
unclear to a newish user what this actually means. (It took me some
time to figure it out, and I've got 20 years programming experience!)
I would therefore humbly suggest that the "fixed in CVS" message should
read something like this:
There is already a fix for this bug in the latest development
version
("CVS") of PHP -- this should appear in version
4.2.9, or you can obtain a snapshot of the CVS version at
http://snaps.php.net/.
If this was a documentation problem, the fix should show up soon at
http://www.php.net/manual/. If this was a PHP.net
website problem
... etc.
(Of course, this brings up a subproblem of version numbering if an
emergency release is made in the interim, as happened with 4.2.2 -- I
guess this would just be a greater incentive to make such releases as a
pl rather than a full subpoint...!!)
Cheers, and thanks for all your efforts!
Mike
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=18807&edit=1