The following bug have been fixed:
[-] Domain has default SSL Certificate after backup restoring or migration
[-] plesksrv.exe may fails on high load
[-] HTTP traffic and web statistics are not calculated for IDN domains
[-] Migration fails if source server has primary network interface with inaccessible IP address
[-] websrvmng –reconfigure-all can’t restore Plesk Control Panel site on Windows 2008 R2
[-] Error “Version string portion was too short or too long” when backup clean server
[-] IIS logs for PleskControlPanel site stored only one day
[-] Wrong statistic calculating by Webalizer for domain with several aliases
Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it’s easily my favorite. Don’t get me wrong, I love attending WordCamps and local WordPress meetups (which are awesome and you should try to attend if you are able), but at the core team meetup, the focus on working together and getting things done is unique, as is the experience of every person in the room being so highly qualified. This year, instead of just planning a core team meetup, I’m aiming a little higher and shooting for a full-on contributor/community summit.
Core code isn’t the only way to contribute to the WordPress project. We have an active theme review team, support forum volunteers, people writing documentation, plugin managers, community event organizers, translators, and more. The teams have been siloed for too long, so we’ve recently begun the process of bringing them together by having teams elect representatives to facilitate more communication between the contributor groups. These reps will form the nucleus of the contributor summit now being planned for a long weekend at the end of October in Tybee Island, GA. This is completely different from a WordCamp. It will be a combination of co-working, unconference, and discussions among the project leaders, and participation will be by invitation.
In addition to bringing together the active contributor team reps to work together, I think it’s important to include community members who don’t fall into that category (at least not yet!). Successful WordPress-based business, authors of popular plugins and themes, and people using WordPress in unexpected but intriguing ways should have a place at the table, too. That said, part of the magic of the core team meetup is the small size; it allows every voice not only to be heard, but to engage. Since this is my first attempt at bringing together so many groups and points of view, I want to try and keep it small enough to retain that personal atmosphere while at the same time ensuring that the best possible mix of people and businesses in the WordPress ecosystem is represented. This is where you come in!
Taking a cue from events with limited availability like AdaCamp (attendance) and the jQuery conference (speaker roster), I want you to nominate people and/or WordPress-based businesses to participate in the summit. Yes, you can nominate yourself.* You can nominate up to 10 additional people — be prepared to provide URLs and the reason you think they should participate. You can also nominate up to 10 WordPress-based businesses without naming individual people, so if there’s a theme or hosting company (for example) that you think should be there, you don’t need to go looking for employee names. This nomination process will hopefully ensure that we don’t overlook someone who is making a difference in our community when it comes time to issue invitations.
Nominations will be open for a week, after which the survey will be closed and the process of analyzing the results** will begin. The nominations process will lead to invitations in June, confirmations in July, planning in August and September, and the summit itself in October. Hopefully we can stream and/or record some of the activity to share online at WordPress.tv. Additional invitations may be extended up until the event if there are people/businesses that become more active in the community. If you’re thinking to yourself that maybe now’s the perfect time to start contributing time to the WordPress project, good thinking! In the meantime, if you want to weigh in, fill in the community summit nomination form. Thanks, and wish us luck!
* Nominating yourself: Do nominate yourself if you fall into one of the categories described in the post above, or if you believe that you have a unique point of view. Please do not nominate yourself if you just think it would be cool to hang out with this group. This is a working event, and everyone is expected to bring something special to the table.
** I (and/or a helpful community volunteer) will sift through the nominations and compile a shortlist of the most-nominated people/businesses and the most intriguing underdogs. This list will be reviewed by the summit planning committee (made up of team reps) to create the invitation list.
Oracle Enhances MySQL Installer and High Availability for Windows — New Installer Streamlines Deployment, Extends High Availability to Windows Server 2008 R2
[+] MySQL ODBC 5.1.11 driver support has been added
The following bug have been fixed:
[-] XSS vulnerability in Horde IMP has been fixed (CVE-2012-0791)
[-] When admin’s password changing via ch_admin_passwd utility mysqld is running with –skip-grant-tables option
[-] Migration via rsync may fails with “pipe: Too many open files” error
[-] 10.4.4 MU#28 does not set SELinux contexts on /usr/local/psa/handlers/hooks/check-quota handler which causes mail system to go down
| Rank | Company site | OS | Outage hh:mm:ss |
Failed Req% |
DNS | Connect | First byte |
Total |
| 1 | Datapipe | FreeBSD | 0:00:00 | 0.003 | 0.047 | 0.014 | 0.029 | 0.049 |
| 2 | INetU | Windows Server 2008 | 0:00:00 | 0.007 | 0.090 | 0.081 | 0.243 | 0.481 |
| 3 | www.choopa.com | Linux | 0:00:00 | 0.010 | 0.153 | 0.041 | 0.088 | 0.097 |
| 4 | Kattare Internet Services | Linux | 0:00:00 | 0.010 | 0.193 | 0.148 | 0.298 | 0.597 |
| 5 | Swishmail | FreeBSD | 0:00:00 | 0.014 | 0.136 | 0.071 | 0.143 | 0.344 |
| 6 | Multacom | FreeBSD | 0:00:00 | 0.014 | 0.219 | 0.130 | 0.262 | 0.767 |
| 7 | Qube Managed Services | Linux | 0:00:00 | 0.017 | 0.091 | 0.034 | 0.070 | 0.070 |
| 8 | ReliableServers.com | Linux | 0:00:00 | 0.017 | 0.192 | 0.081 | 0.167 | 0.175 |
| 9 | Pair Networks | FreeBSD | 0:00:00 | 0.017 | 0.334 | 0.091 | 0.185 | 0.644 |
| 10 | www.codero.com | Linux | 0:00:00 | 0.021 | 0.157 | 0.061 | 0.355 | 0.626 |
The most reliable hosting company for April was Datapipe, which topped the table seven times in 2011. The company offers a wide range of hosting services and has been rapidly expanding into cloud computing during the past few months. Datapipe has infrastructure spread across the globe; they have data centres in New Jersey, San Jose, Iceland, London, Shanghai, and Hong Kong. Their U.S. data centres are powered exclusively by renewable energy sources.
For the third time so far this year INetU have taken second place. INetU offers dedicated managed hosting services and cloud hosting services from data centres in both the United States and Europe.
Choopa – a New Jersey based company advertising 100% uptime and 0% packet loss guarantees – appears in third position for the second consecutive month.
Linux was used by five of the most reliable hosting companies, including Choopa; four used FreeBSD including the most reliable, Datapipe; and the second most reliable provider, INetU, used Windows Server 2008.
Netcraft measures and makes available the response times of around forty leading hosting providers’ sites. The performance measurements are made at fifteen minute intervals from separate points around the internet, and averages are calculated over the immediately preceding 24 hour period.
From a customer’s point of view, the percentage of failed requests is more pertinent than outages on hosting companies’ own sites, as this gives a pointer to reliability of routing, and this is why we choose to rank our table by fewest failed requests, rather than shortest periods of outage. In the event the number of failed requests are equal then sites are ranked by average connection times.
Information on the measurement process and current measurements is available.