php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #62016 Bug DB canned answers still refer to SVN
Submitted: 2012-05-13 21:32 UTC Modified: 2012-09-16 21:17 UTC
From: stas@php.net Assigned: tyrael (profile)
Status: Closed Package: Website problem
PHP Version: Irrelevant OS: *
Private report: No CVE-ID: None
 [2012-05-13 21:32 UTC] stas@php.net
Description:
------------
"Quick Response" answers in bugs.php.net still refer to SVN. Unfortunately since 
these seem to be stored in a database, it is not possible to fix them via git. 
Somebody needs to go to the DB and actually change them there. 


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2012-05-13 21:36 UTC] tyrael@php.net
some stuff (like pecl, phpdoc) is still in SVN.
should I replace SVN with VCS in the quickfix texts?

Tyrael
 [2012-05-13 23:22 UTC] stas@php.net
That, or have different answers depending on bug package/type, I think.
 [2012-08-20 05:33 UTC] aharvey@php.net
Duped by bug #62868.

Somebody with access to the bugdb database needs to do this, since these aren't stored in code.
 [2012-08-24 20:02 UTC] tyrael@php.net
Stas, I looked into the issue.
we support adding different resolution text for a quick fix by status and 
package name.
when Felipe merged the pecl bugtracker with bugsweb he also added the some 
infrastructure to support different resolves per project (php, pecl), but that 
isn't complete.
The only problem is that if we want separate quick fix/resolves for pecl, we 
have to duplicate the current ones for pecl, and I would like to know if we do 
that, what quick fixes should we keep for pecl.

I also wanted to mention that even the pecl exts aren't all in svn, as we allow 
to host the code on github, etc.
Maybe it would better to re-word the text to be vcs agnostic, so not specific to 
svn or git.

What are your thoughts?
 [2012-08-24 20:03 UTC] stas@php.net
rewriting it in VCS-agnostic way would be a good idea.
 [2012-08-24 20:30 UTC] tyrael@php.net
https://bugs.php.net/quick-fix-desc.php

Fixed in SVN

could be
Fixed in VCS
but I think that it isn't that well known for our users.
I would prefer
Fixed in Source
or
Fix Committed


This bug has been fixed in SVN.

could be
This bug has been fixed in the repository
or
The fix for this bug has been committed.


Since the websites are not directly updated from the SVN server

could be 
Since the websites are not directly updated from the repository


Since the PHP Documentation Tools website is updated from the SVN repository

could be
Since the PHP Documentation Tools website is updated from the repository


Could you please review these changes before I update the messages in the db?
 [2012-08-24 20:55 UTC] stas@php.net
I'd go with some variation of "the fix for this bug has been committed".
 [2012-08-27 01:10 UTC] kriscraig@php.net
Reposting this from Internals per Ferenc's request:

Hey guys,

I'm not sure whom to ask, but could somebody with the appropriate privs add a 
"Quick Fix" to the Bugs dropdown that says something along the lines of, 
"Support for this PHP version has been discontinued (won't fix)"?  There's 
currently a similar one already but it's specific to PHP 4, and there are PHP 
versions since then that we no longer support (i.e. <= 5.2.x).


Thanks!

--Kris
 [2012-09-16 21:17 UTC] tyrael@php.net
Stas: I've updated the db using the vcs agnostic wording.
Kris: I think "Try newer version" should be what you are looking for.(see 
https://bugs.php.net/quick-fix-desc.php for the message of each quick fix)
 [2012-09-16 21:17 UTC] tyrael@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: tyrael
 
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Sat Feb 29 02:01:28 2020 UTC