Re: Services_Digg not valid?
| From: | Helgi Þormar | Date: | Sun, 20 May 2007 12:08:05 +0000 |
| Subject: | Re: Services_Digg not valid? | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.webmaster |
| Request: | Send a blank email to pear-webmaster+get-5905@lists.php.net to get a copy of this message | ||
Moving this to pear-webmaster
On 5/20/07, Mark Wiesemann <wiesemann@php.net> wrote:
Helgi Þormar wrote: On 5/20/07, *Martin Jansen* <martin@divbyzero.netThat was more of my fault, well I take the full blame for DB_Storage removal, tho more people should have tested it before it went live, that's for sure, it's no excuse to say "but there were no unit tests", f.ex. everything I tried worked but apparently didn't catch everything (as one might expect since no one can really test _everything_) So basically atm we have a way that shouldn't introduce this kind of things (and will even more so when more unit tests trickle in) but also the new way hinders us to do bug fixes that fix exactly this kind of situations. So perhaps more webmaster need to have terminal access so we can react faster ? There have been times where David and I are just helpless since we do know the cause, already committed it to cvs but have to wait for someone with proper access to fix the live site :) Be it by patching the file or rolling a minor release (iirc we don't do branches atm so when say 1.5 dev has started then it's a bit hard to do another 1.4 release) Any comments or ideas how we can improve upon this? - HelgiI manually fixed the file on the server so that we do not have towaituntil the next release of the pearweb package for this change to hit the site.This is partially why I'm not all that happy with the fact that we only release the website like a package, only a handful of people or less can do live updates and those people aren't always around :) There are exactly two people that can do these kind of fixes. Especially for bug fixes we should try to find a better and faster solution. The old way with direct syncing from CVS to the website was also not perfect, of course. But the new way has also its problems: slow bug fixes, half-finished (and untested and broken) things go into the website etc.