If only 4 files are changed between two releases, why force everyone to reinstall the whole thing? Why not a patch or just a zip of the affected files? This is a must! I know upgrades are reasonably fast, but it’s just not logic to download the whole package every single time (about every two weeks…), and have to manually delete a folder, decompress, etc.
Point two: I hope the next major release is tested a lot more! WordPress is loosing credit due to all these minor updates and bugs. I’ve recently read this in a blog’s comment: “Even Microsoft doesn’t release a new OS each time they find a bug that is fixable with a simple patch”. I’d be worried if an open source project I worked on is compared to Windows.
Point three: What’s all that “(…)but an important security issue was brought to our attention which required an update for our users. The problem is not yet public but you should update your blog as soon as possible…” This is amazing! I thought open source meant open mind. You just can’t give something to your users and tell them to install it without telling them why. I deserve to know what I am installing, what has changed and more important: why! I thought only commercial software companies did Security Through Obscurity. Come on, the WordPress team can do better. We’ve seen you do better!
Besides all the above, I know that WordPress is a community effort and I appreciate the time each member dedicates to make WordPress the best CMS ever. This shouldn’t be taken as a rant against WordPress developers, just as a little “hey, let’s not forget that we know how to do things better”, ok?
- The topic ‘How about patches?’ is closed to new replies.