Add the whole blog

This commit is contained in:
Luca Beltrame 2020-12-28 18:06:15 +01:00
parent 0d2f58ce7a
commit c4f23c1529
Signed by: einar
GPG key ID: 4707F46E9EC72DEC
418 changed files with 15708 additions and 0 deletions

View file

@ -0,0 +1,21 @@
---
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'
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?