Milestones when valid Atom was supposed to be supported by WordPress:
Did I mention that
WordPress 2.1 shipped yesterday?
To add support for Atom 1.0 you will
have to follow the directions here.
Geof F. Morris on 2007-01-23
rick on 2007-01-23
We aren't talking about Atom Publishing Protocol support, which is still just in draft form, we are talking about the Atom Syndication Format, which has had an RFC number for over a year now.
joe on 2007-01-23
Jason on 2007-01-23
Devon on 2007-01-23
Asbjørn Ulsberg on 2007-01-24
Although I'm really angry about this -- because once upon a time I thought the project was being run by the kind of people who cared about things like Atom 1.0 -- you're not being fair.
RFC4287 is dated December 2005. There wasn't enough time to squeeze it into the release of WordPress 2.0 and be sure of aggregator support. BlogLines' patchy support was cited as a specific reason for keeping it out, for example. The (perfectly reasonable) argument was that users would blame WordPress for "breaking" their feeds. That cuts seven milestones down to two.
It's more shameful, but Atom 1.0 was kept out of WordPress 2.1 because, as your list shows, it had already taken a year to ship: a whole lot of things were left out just to get the release out the door. It's likely to be in 2.2, which already has preliminary APP support.
Norman Gerre on 2007-01-24
alf on 2007-01-24
Matt on 2007-01-24
Sam has pointed out a few that are already available, and he has offered to fix any shortcomings, and even make sure they validate.
I'm thrilled to hear about the APP support
and will be checking it out soon.
joe on 2007-01-24
Eric Larson on 2007-01-25
© 2002-14 Joe Gregorio