Edit report at https://bugs.php.net/bug.php?id=62016&edit=1
ID: 62016 Updated by: [email protected] Reported by: [email protected] Summary: Bug DB canned answers still refer to SVN -Status: Open +Status: Closed Type: Bug Package: Website problem Operating System: * PHP Version: Irrelevant -Assigned To: +Assigned To: tyrael Block user comment: N Private report: N New Comment: 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) Previous Comments: ------------------------------------------------------------------------ [2012-08-27 01:10:16] [email protected] 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-08-24 20:55:17] [email protected] I'd go with some variation of "the fix for this bug has been committed". ------------------------------------------------------------------------ [2012-08-24 20:30:29] [email protected] 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:03:46] [email protected] rewriting it in VCS-agnostic way would be a good idea. ------------------------------------------------------------------------ [2012-08-24 20:02:28] [email protected] 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? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=62016 -- Edit this bug report at https://bugs.php.net/bug.php?id=62016&edit=1 -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
