Comments on: s/2.4/2.5/g

By: Upgrading to WordPress 2.5 or not? « WP Stuff

Upgrading to WordPress 2.5 or not? « WP Stuff — Wed, 19 Mar 2008 23:19:39 +0000

[...] think I’m actually looking for and want the missing 2.4 edition, the version they ate for Christmas, which again make me believe the development of WordPress going too [...]

By: Kommet

Kommet — Sun, 03 Feb 2008 14:46:01 +0000

@Keith, re: Sam

Thanks to the WordPress team. What more could we request of such a great, free system? Regards,

@My Parents

Thanks for trying to make me bilingual. It didn’t quite work, but at least I can dispense with Babelfish for reading Spanish (and some Portuguese and a little Italian and French, thanks to the Romans).

@Ryan and Keith

Hey, if you are gonna do date-based releases (like Ubuntu, GNOME, etc.), the trick is to know your workflow and set dates accordingly. Sounds to me like that is what this is.

@TacoBiter

What’s in a name? A release by any other number would contain the same code.

Seriously, though, It’s probably easier to just move work (tickets) from 2.4 to 2.5, rather than moving 2.5 to 2.4, 2.6 to 2.5, not confusing those moves (2.6 to 2.5 to 2.4, or leaving 2.5 tickets in place), and then explaining to any random onlooker than no, feature X or bugfix Y didn’t get moved up 3 months. Ryan (or anyone else from Automatic) is free to correct me, but at least in my job if we decide to skip a release and already have subsequent releases on the roadmap we don’t renumber everything up by one precisely so that conversations don’t get confused.

By: Benedict Eastaugh

Benedict Eastaugh — Sun, 03 Feb 2008 12:50:55 +0000

Keith, the roadmap exists for several reasons. Firstly, there was a lot of demand for it: WordPress is now a very big player, and there are big companies and institutions relying on it. A roadmap means people don’t have to follow development closely to have a decent idea when the next major release will be. Secondly, it makes development cycles faster and hopefully more effective: deadlines give a release focus, and hopefully ensures a bit of realism: with a set period of time in which to complete each release, only a certain amount of stuff can make it in, which means important decisions about feature priority are actually taken, and releases mostly happen on schedule rather than taking months and months (and sometimes even years) because all the stuff the developers would love to pack into the next version still isn’t finished. At the end of the day the roadmap is about making the developers’ lives easier and allowing WordPress users more insight into the development cycle without forcing them to read every Trac ticket.

By: Chukles

Chukles — Sun, 03 Feb 2008 05:30:03 +0000

The number of releases are not an issue for me. Instead the issue for me is from a user perspective that the release does not add more work for me (i.e. more clicks to do the same thing) nor does it make installing the release more complex. For me from a from a quality standpoint regarding the release that the release as been tested, any significant errors have been corrected (e.g. security issues) before the release is made available for download, and any known issues including compatibility issues are made known at the time of making the release available for download.

By: Keith Bowes

Keith Bowes — Fri, 01 Feb 2008 19:01:09 +0000

@Ryan: Why have roadmaps at all? Just decide what you’re going to do at the concerned version and release after that’s done and tested.

@Chris: I agree. There’s nothing like being childless (I used to babysit as a teenager, so I know what a pain kids are) to allow you to get work done on your time off.

@Sam: Que? I think it’s something to do with apples but I’m not sure.

@TacoBiter: My sentiments exactly.

By: btard

btard — Thu, 31 Jan 2008 06:22:22 +0000

You’re doing the March (spring) thing because it’s my birthday month, right?

By: Zie

Zie — Wed, 30 Jan 2008 15:53:49 +0000

Awesomeness. If enough new features warrants skipping a version, then why not. Sounds good.

By: Luca Beltrame

Luca Beltrame — Wed, 30 Jan 2008 11:20:13 +0000

As long as it doesn’t break the DB schema just one month before release (like 2.3 did), it should be fine.

By: TacoBiter

TacoBiter — Tue, 29 Jan 2008 21:31:31 +0000

Lame. Just lame. call it 2.4.

By: Jonathan

Jonathan — Tue, 29 Jan 2008 19:17:13 +0000

This is so much better than the 1.5 days, when releases came on a whim. I checked my dashboard daily—even if I wasn’t posting—just to see what was happening in the release department.

Thanks. (That word does a terrible disservice compared to what you guys actually deserve)