Luca Beltrame
64b24842b8
All checks were successful
continuous-integration/drone/push Build is passing
22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
---
|
||
author: einar
|
||
categories:
|
||
- General
|
||
comments: true
|
||
date: "2007-10-07T19:01:33Z"
|
||
slug: unimpressive-management-wordpress-23
|
||
tags:
|
||
- wordpress
|
||
title: 'Unimpressive management: Wordpress 2.3'
|
||
omit_header_text: true
|
||
disable_share: true
|
||
wordpress_id: 297
|
||
---
|
||
|
||
I've recently upgraded this blog to [Wordpress 2.3](http://wordpress.org). While I'm interested in the new changes this release brings (like tagging support) I question the way the transition to the new version was handled.
|
||
|
||
In particular, I am referring to the (questionable) [idea of breaking the database schema three weeks before the release](http://boren.nu/archives/2007/09/05/wordpress-23-database-schema-changes/). Given the amount of breakage that brought upon plugins, it should have been announced at the start of the 2.3 development cycle. Right now, heavily customized installations are a pain to update (that's why [_The S.T.E.A.L. Saga_](http://www.stealsaga.net) is staying on 2.2 for now).
|
||
|
||
I think the WP guys should look at how bigger projects like [GNOME](http://www.gnome.org) or [KDE](http://www.kde.org) are handled regarding such aspects. They can't really expect to break an API every release, can they?
|
||
|
||
On a related topic, I'm thinking of changing the theme of this blog. Has anyone got any recommendations?
|