#18807 [Opn->Bgs]: Please quote likely version number in "fixed in CVS" message
| From: | kalowsky@php.net | Date: | Wed, 14 Aug 2002 02:09:00 +0000 |
| Subject: | #18807 [Opn->Bgs]: Please quote likely version number in "fixed in CVS" message | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-16674@lists.php.net to get a copy of this message | ||
ID: 18807
Updated by: kalowsky@php.net
Reported By: m.ford@lmu.ac.uk
-Status: Open
+Status: Bogus
Bug Type: Feature/Change Request
Operating System: n/a
PHP Version: 4.2.2
New Comment:
I believe 4.2.2 was an exception to the usual. It was an emergency
security fix. Typically any fixes that are applied to CVS HEAD (which
is the fixed in CVS message) are also applied to the latest branch. In
some cases this cannot happen due to some chagnes (i.e. the new build
system). Because of this I'm going to mark this as Bogus, because
honest, we do usually back port these fixes!
Previous Comments:
------------------------------------------------------------------------
[2002-08-09 07:23:15] m.ford@lmu.ac.uk
I, in turn, see your point ;) !!
However, your proposed wording is not necessarily any better, as "next
released version" isn't always true (again, witness all the stuff
that's fixed for 4.3.0, but didn't make it into 4.2.2 -- and even
wouldn't have into 4.2.3 if it hadn't been killed!). How about noting
that the fix will appear in a future release, and advice to keep an eye
on the change log (complete with link), so maybe something like:
A fix for this bug is already included in a development version
("CVS") of
PHP, and should appear in a future release -- the ChangeLog at
http://uk.php.net/ChangeLog-4.php will let you
know when a version
is
released including this fix. Alternatively, you can obtain a
snapshot ...
Oh... ummm... another subissue... Better quoting of bug numbers fixed
in the ChangeLog?
Cheers!
Mike
------------------------------------------------------------------------
[2002-08-08 11:58:34] tal@php.net
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
------------------------------------------------------------------------
[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