INSERT INTO sites(host) VALUES('dd32.id.au') 144: Table './myip/sites' is marked as crashed and last (automatic?) repair failed dd32.id.au 网站价值¥417,334(不含域名),MYIP.CN网站综合数据统计 - 域名,Alexa,PR,反向链接,关键字
  测网速 网站优化诊断 广告招商QQ3066631932 CodeForge最好的源码站!   手机测速 测速APP

  
                       

网站页面信息

标题:
描述:
关键字:
sponsored links:
连接:
图片:
网站历史:
sponsored links:

网站流量与估价

网站流量:
网站估价:  (注:不包含域名价值,不代表公司价值)

网站排名

Alexa全球排名:
Google Page Rank:
真假PR鉴别:   (提示:若此处显示网站与查询网站不同,则疑为劫持PR)
Sogou Rank:
百度快照日期:

搜索引擎收录

搜索引擎收录情况反向链接
 谷歌Google:
 百度Baidu:
 微软Bing:
 搜搜Soso:
 雅虎Yahoo:
 有道Youdao:
 搜狗Sogou:

服务器信息

Web服务器:
IP地址:    
IP所在地:

域名注册信息

注册人:
Email:
ICANN注册机构:
创建时间:
修改时间:
过期时间:
状态:
Name Server:
Whois Server:

Alexa 排名走势数据

流量统计: 当日 一周平均 三个月平均
排名:
PV:
日独立IP:

网站在各国/地区的排名

国家/地区访问比例

下属子站点被访问比例

Alexa 排名走势图

Alexa Reach走势图

域名 Whois 记录

网站缩略图

sponsored links:

网站访问速度测试

国内Ping速度测试      国内TraceRoute路由测试
美国Ping速度测试      美国TraceRoute路由测试

网站关键字指数 (越高越热门)

域名 dd32 其他后缀注册情况   查看更多

后缀 注册时间 到期时间 是否注册
.com
.net
.org
.cn
.com.cn
.asia
.mobi

同类相似网站

查看更多

模拟搜索引擎蜘蛛抓取

Title:A Call to Arms – blog://dd32.id.au/
Description:
Keywords:
Body:
A Call to Arms #8211; blog://dd32.id.au/
Skip to content
blog://dd32.id.au/
Projects
WordPress.org Plugin Information API Docs
Soon to be Released Project 1
Wordpress Plugins
Add From Server
dDeviantArt
Remove Max Width
Revision Control
Search Redirector
TorrentPress
Contact Me
Log in
Categories:
General
Local
Opinion
Photography
Prefixed
Aside
Computers
Gallery
Kyogle Flood
Personal
PHP
Programming
Review
Site
Something Cool
Summer of Code
WordCamp
WordPress
WordPress Plugin
WTF
[WordPress] A Call to Arms
WordPress 2.9 was just released, And several users have run into a bug. Surprising? Not really. Theres one simple reason for this, While thousands of people Test each and every WordPress release, These users are not You.
I #8217;d like to use this as an example to all here, Why WordPress needs your help. No, I #8217;m not talking about Coding help specifically, I #8217;m talking about Testing. WordPress requires that users test the product throughout the development period.
WordPress is an open source application written by hundreds of contributors. While those hundreds probably use the Development version of WordPress every day, They do not use the same webhost as you, nor do they have the same theme, nor do they have the same requirements, They use different functions of WordPress than you.
During The beta and RC stages, thousands of people download and test, These testers are end users like you, In order to prevent these bugs getting into a released product, It requires that users actually take part in the developement of WordPress and report the bugs encountered.
Testing WordPress is not just something that Developers should do. If you use WordPress and enjoy using it, Please take some time once every few months to test WordPress, Its announced on the Dev blog when Beta #8217;s are available, On a default install of WordPress, The Dashboard should have a RSS feed mentioning the releases too.
So please, For 3.0, When a Beta is released (Theres generally ~2-3 weeks of beta, with 2-3 beta #8217;s from my quick recolection) Install it on your website, It doesnt have to be your main one, it can be in a subdirectory (ie. your usual one at http://my-site.com/ and the test at http://my-site.com/testing/), and test that things works ok for you, and your plugins, This does take an hour out of your time, and i realise not everyone can afford it, But it may spare you 2-3 hours of your time, when after a release, a bug that affects you is found, that a Developer had not noticed.
WordPress requires your input, Whilst I agree there are some downfalls in reporting bugs sometimes (Please do not flame me with related messages here, I #8217;m not after that, This is mearly a request for more contributions) overall, your contributions would be greatly appreciated by all.
In order to make it easier to test Beta #8217;s and nightly versions, Westi wrote this great plugin It allows you to use the inbuilt upgrader to upgrade to a beta, to make it easier for you, to be involved with the project you love using.
Posted in Opinion, WordPress.
Tagged with development, testing, trunk, WordPress.
18 comments
By DD32
ndash; 21 December, 2009
18 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.
Rajesh Kanuri @ TechCats says
It is similar problem existed when wp is upgraded form 2.6 to 2.7 and it repeated again.. Hope they wont overlook this in 3.0
21 December, 2009, 8:00 pm
Reply
DD32 says
A similar problem happens every release. Not enough people test on their host, and the result is, that a untested server configuration is hit. When you consider that Developers probably make up 0.05% of total installs, and beta testers maybe 0.1% Its impossible to cover every branch.
As an example, So far there have been 320,000 downloads of WordPress 2.9. There were 140 identified contributors to WordPress 2.9, Lets assume that out of those 320k downloads, 10% were on unique server setups, thats 32,000 server configurations, Thats 230, Two Hundred and Thirty different Server configurations PER CONTRIBUTOR, Its impossible for developers to do that testing.. Testers are required.
The more testers there are, The more server configurations are tested, and functions, Its impossible for them to all be covered #8230;
21 December, 2009, 8:07 pm
Reply
DD32 says
Thats just based on Server Configuration, If you take into account that different features work different on different servers, the testing list can grow even larger.
21 December, 2009, 8:12 pm
Reply
miqrogroove says
Hi DD32. I agree with the body of the message. I must point out, however, that the bug you referenced at the top did not exist in any of the beta or RC versions of WordPress. This bug was introduced *without testing* immediately before release as described in Ticket #11468
22 December, 2009, 12:17 am
Reply
DD32 says
I do agree that particular changeset was pushed in late, due to a known issue with another transport.. In retrospect, The changes to the other transports should #8217;ve been delayed but at the time, seemed to make sense according to the docs available.. and testing on the servers that were tried.
This is not the -only- issue in this release, just as it is every release, There #8217;s always some kind of bug which affects some which never surfaces until a few hours after release.. My point was more of a generic one, even though it was spured from the pointed out item. Its something i hear every release, and if people were to test more, it #8217;d be less likely to happen #8211; I #8217;d throw a comment in here about #8216;damn php bugs #8217; but i know someone will just flame me for passing the buck..
22 December, 2009, 1:00 am
Reply
miqrogroove says
gt; changes to the other transports should’ve been delayed
I must respectfully disagree. This is a situation that demands a second release candidate. Any non-trivial change to something like the HTTP API should be given weeks of testing.
22 December, 2009, 1:54 am
Reply
John Myrstad says
As proposed in dev talks a clone solution to run a clone of online site on a test install will help to find those bugs testers dont find.
If I remember correct Matt`s respons was that its not any lack of testers. I there was 10.000 + installs of beta/RC.
John Myrstad
22 December, 2009, 6:34 am
Reply
DD32 says
I personally dont give a crap about what Matt thinks. Its all opinion.
And in my opinion, Due to the vast number of servers out there and the configurations in which people use wordpress, More testers will -always- be needed.
I #8217;m not sure what you mean about a Clone solution? By running a copy of a production site, you are infact, a tester.
22 December, 2009, 10:48 am
Reply
Jane Wells says
Number of testers as counted by the number of people who #8217;ve downloaded the beta or RC is very different from the number of people who actually report bugs, which is even still different from the number of people who report bugs and provide enough information to make it reproducible and thus fixable. I #8217;m with Dion here, we need more testers, and more specifically, we need more testers who are willing to follow a published QA process. (Which, of course, means we #8217;d need to have a published QA process!)
Seriously, though, they #8217;re both right. We do have a lot of people who download early trunk versions and give them a spin, but very few who run automated tests or even manually review each change and report back on the performance on their setups. I think creating a section on WordPress.org with instructions for testing, maybe with a simple QA form that can be submitted, would help us get more high-value testers. The easier we can make it, the better off we #8217;ll be.
23 December, 2009, 12:49 am
Reply
miqrogroove says
I #8217;m repeating myself, but the number of testers doesn #8217;t mean a damn thing unless someone fixes the bugs that are reported. I put so much effort into writing patches and screaming about known bugs during this beta cycle, that I didn #8217;t even get around to reporting all the bugs I found, let alone test everything.
23 December, 2009, 4:23 am
Reply
Jane Wells says
And the patches need to be tested by more than one or two people before they are evaluated for commit. You #8217;re making the case for more testers without apparently realizing it. If more things were tested at the level they are meant to be before being reviewed for commit, the core commit team could get through patch reviews faster, and patches wouldn #8217;t languish.
23 December, 2009, 8:29 am
Reply
miqrogroove says
This article had nothing to do with testing patches before commit. If you #8217;re saying there aren #8217;t enough people involved in Trac, I think that #8217;s a whole separate topic.
23 December, 2009, 9:13 am
John Myrstad says
If bugs are found earlier, it will be more time to test, debug and patch.
If someone could collaborate on a Clone WP Plugin, which makes it easy to set up a local or subdomain clone of a live site, more medium skilled people will run RC`s to prepare their site for the upgrade which may lead to more bugs found early.
Some code which may be used in such plugin is made by Dave Coveney: http://www.davesgonemental.com/mysql-database-search-replace-with-serialized-php/
23 December, 2009, 7:06 am
Reply
Sadekya says
I cant understand why they cant have automated tests and put them through the grind. Manually reviewing each change and then reporting back on the performance on their setups is fraught with too many whims/
23 December, 2009, 7:59 pm
Reply
sam says
I have been patient but really these bugs need to be tested more thoroughly with new updates, I know its impossible to get everyone #8217;s bugs resolved but I have a wish list for the next wordpress update:
1) Please fix the #8220;spelling correction button #8221; on Writing Posts I often am in a big hurry. I have to spell check each post and you know it picks up false positives, and then freezes up on my and doesn #8217;t work further. I wish you would have a better spell checker on WP, and a grammar fix would be nice too.
Yes some people will say why don #8217;t you write it first in word then spell check then bla bla bla #8230;.C amp;P #8230;.well that defeats the whole purpose of writing a post freely within WP posting area, and the editing function. I want it to work properly when I am writing an article -that #8217;s about it.
Wish Number Two: would be to have an Archive that gives you the option of displaying post titles instead of just categories, this is a great SEO function as well that I would like to use, have each post displayed as a link #8211; not just the months of the year.
If I were a reader #8211; How would I know what subject title was written 3 months ago gt; its makes it harder for people to find posts.
If anyone has a plug or two that does the above mentioned -it would be appreciated to find it -where ever it is hidden. I don #8217;t do codes, and PHP #8230;I am a writer #8230;.and the easier these #8221; Techey #8221; things are #8211; the less stress in my life.
Sam
28 December, 2009, 3:22 am
Reply
Jane Wells says
Hi Sam. I recommend After the Deadline as a plugin for better spell checking and grammar checking. It #8217;s in the repo, so you can install it right from your #8220;Add New Plugins #8221; screen.
28 December, 2009, 3:55 am
Reply
Continuing the Discussion
2.9.1 Around The Corner laquo; Weblog Tools Collection linked to this post
on 23 December, 2009
[...] contributor to the WordPress project illustrates this problem quite well in a blog post entitled WordPress, A Call To Arms. I think Dion says it best in the first paragraph which illustrates the lack of testing problem [...]
Joe Jacobs raquo; Blog Archive raquo; Tweets for the week ending 2009-12-27 linked to this post
on 27 December, 2009
[...] @Viper007Bond A Call to Arms by @dd32 http://dd32.id.au/2009/12/21/a-call-to-arms/ Comon people, help test WordPress! [...]
Leave a Reply Cancel
Some HTML is OK
Name (required)
Email (required, but never shared)
Web
or, reply to this post via trackback.
Notify me of followup comments via e-mail
laquo; Dear cute girl I passed today:
Subscribe
About blog://dd32.id.au/
A Message from DD32:
Hi all, I #8217;m Dion Hulse, a 22 year old from Regional Australia.
As you can probably tell by some of the content on here, WordPress is my passion, Plugins and Custom applications #8211; Thats what i enjoy doing. And yes, I am available for hire.
Archives
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
January 2008
October 2007
September 2007
August 2007
July 2007
June 2007
April 2007
March 2007
Tags
$$$
3D
add-from-server
animation
api
aside
BOM
cebit
CSS
DD32
ddeviantart
december
DeviantArt
filesystem
Flood
floppy
Gallery
gallery2
GSoC
Kyogle
Kyogle Flood Jan 2008
Media
MSN
nokia
Opinion
Photography
photos
PHP
pics
plugin-installer
Plugins
rant
review
revision-control
Site
sydney
theme
video
weather
wordcamp
WordPress
wordpress automatic installer
WordPress Plugin
Wordpress Plugins
wp-update
Proudly powered by WordPress and Carrington.

数据更新时间

正在更新   

常用工具

桌面软件: MyIP网站信息状态条  WebShot网页快照  SiteMapMaker网站地图生成 
网站信息: Alexa排名查询  PageRank查询/真假PR鉴别/PR劫持检测  外链检查  搜索引擎收录  搜索引擎