Comments on: WordPress 2.2 Release Candidate 1 Now Available

By: WordPress 2.1 fan

WordPress 2.1 fan — Sat, 19 May 2007 16:55:52 +0000

Dougal, well, I guess that is the disadvantage of not been a professional WP coder, like myself. I make the theme, it works, then I figure it does not even displaying properly in IE (as I work in FF) and when I tried to upgrade using my test blog, the widgets and some other fancy enhancements ended up been a lil` screwed up. Not to you have mentioned it, I don’t know if it interrupts or interfering with the API key. I’d have to check as I have no clue..

By: geek ramblings :: WordPress 2.2 Release Candidate 2 Now Available

geek ramblings :: WordPress 2.2 Release Candidate 2 Now Available — Mon, 14 May 2007 14:31:55 +0000

[...] Skip navigation About This SiteArchivesDonateContactWeight GoalThe Car Tag Saga « WordPress 2.2 Release Candidate 1 Now Available [...]

By: Dougal

Dougal — Mon, 14 May 2007 13:59:04 +0000

Arun: There are no real changes to the category system in the 2.2 release. The 2.3 release, will have a major overhaul to the category system to accomodate tags and other alternate taxonomies.

WordPress 2.1 Fan: Normally, there shouldn’t be any theme issues with upgrades to core, unless you are bypassing the API in some way.

By: WordPress 2.1 fan

WordPress 2.1 fan — Sun, 13 May 2007 17:40:39 +0000

To be honest, I think WP upgrade their versions far too fast, I still didn’t manage to make the upgrade to 2.1 version and bah, 2.2 is on the horizon. Also, as I make my own WordPress theme, it’s a pain sometimes as some themes or elements end up incompetible with the newer version and this means I gotta somehow test them all with the new release.

By: Links for 5/13/07 [my NetNewsWire tabs]

Links for 5/13/07 [my NetNewsWire tabs] — Sun, 13 May 2007 17:23:43 +0000

[...] geek ramblings :: WordPress 2.2 Release Candidate 1 Now Available — Willing to take a walk on the wild side? “Changes, and such.”:http://codex.wordpress.org/Version_2.2 [...]

By: Arun

Arun — Sun, 13 May 2007 08:48:57 +0000

Are post and link categories separated in this version? Please say yes.. Please!

By: Dougal

Dougal — Fri, 11 May 2007 13:33:30 +0000

Future posts still do not work

If you find a bug, old or new, please report it on the WordPress Trac site, and also to the wp-testers mailing list. Include as many details as you can, including the steps needed to reproduce the problem, if possible.

Oh, and I just tried a future post, and it worked just fine for me. Make sure that your timezone offset is set correctly in Options/General. Depending on what you’re doing, that could have an effect.

By: Jonathan

Jonathan — Thu, 10 May 2007 20:26:36 +0000

@Dougal

Gracias. I shall sw directly.

@Radek

Well, poop. I was really hoping that would get ironed out.

By: Radek

Radek — Thu, 10 May 2007 10:51:04 +0000

Future posts still do not work :-((

By: Dougal

Dougal — Wed, 09 May 2007 21:50:43 +0000

We only tag full releases. Ongoing development happens in branches (or in trunk). So what you’re looking for is:

http://svn.automattic.com/wordpress/branches/2.2

Bugfixes will continue to be committed in there. When the code is considered release-worthy, it will be copied over to ‘…/tags/2.2′, which will always be a snapshot of the code at the time of official release. But any subsequent patches will continue to go under ‘…/branches/2.2′, and if necessary, release snapshots would be made as ‘…/tags/2.2.1′, etc.

Normally, the current RC code wouldn’t be in a branch, it would just be the trunk. But with the decision to back out tags until 2.3, we currently have an abnormal situation where there is active development along two branches (2.2 and trunk, AKA 2.3).