O:9:"MagpieRSS":17:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:10:{i:0;a:13:{s:5:"title";s:20:"WordPress Foundation";s:4:"link";s:62:"http://wordpress.org/development/2010/01/wordpress-foundation/";s:8:"comments";s:71:"http://wordpress.org/development/2010/01/wordpress-foundation/#comments";s:7:"pubdate";s:31:"Fri, 22 Jan 2010 05:38:09 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:31:"Metacharityfoundationnon-profit";s:4:"guid";s:40:"http://wordpress.org/development/?p=1179";s:11:"description";s:314:"It is with extremely great pleasure that I point you to the first post at the new WordPress Foundation site. Not only am I excited about the things that will happen under the auspices of the Foundation, I&#8217;m excited to see a site running the 3.0 development version and the nascent theme called 2010. Go [...]";s:7:"content";a:1:{s:7:"encoded";s:517:"<p>It is with extremely great pleasure that I point you to the <a href="http://wordpressfoundation.org/2010/getting-off-the-ground/">first post</a> at the new <a href="http://wordpressfoundation.org/">WordPress Foundation site</a>. Not only am I excited about the things that will happen under the auspices of the Foundation, I&#8217;m excited to see a site running the 3.0 development version and the nascent theme called <em>2010</em>. Go <a href="http://wordpressfoundation.org">check it out</a> for yourself.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:67:"http://wordpress.org/development/2010/01/wordpress-foundation/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"1";}s:7:"summary";s:314:"It is with extremely great pleasure that I point you to the first post at the new WordPress Foundation site. Not only am I excited about the things that will happen under the auspices of the Foundation, I&#8217;m excited to see a site running the 3.0 development version and the nascent theme called 2010. Go [...]";s:12:"atom_content";s:517:"<p>It is with extremely great pleasure that I point you to the <a href="http://wordpressfoundation.org/2010/getting-off-the-ground/">first post</a> at the new <a href="http://wordpressfoundation.org/">WordPress Foundation site</a>. Not only am I excited about the things that will happen under the auspices of the Foundation, I&#8217;m excited to see a site running the 3.0 development version and the nascent theme called <em>2010</em>. Go <a href="http://wordpressfoundation.org">check it out</a> for yourself.</p>
";}i:1;a:13:{s:5:"title";s:29:"2010 Open Source Design Plans";s:4:"link";s:65:"http://wordpress.org/development/2010/01/2010-open-source-design/";s:8:"comments";s:74:"http://wordpress.org/development/2010/01/2010-open-source-design/#comments";s:7:"pubdate";s:31:"Wed, 13 Jan 2010 20:38:57 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:23:"CommunityUser Interface";s:4:"guid";s:40:"http://wordpress.org/development/?p=1154";s:11:"description";s:332:"2010 is the year we dive into open source design. We&#8217;ve dipped our toes in this pool before (icon contest, graphic design component for Trac tickets, header refresh contest, etc.), but this year we&#8217;re going to cannonball and make a big splash. Here&#8217;s what you need to know if you want to get involved.
A list [...]";s:7:"content";a:1:{s:7:"encoded";s:3855:"<p>2010 is the year we dive into open source design. We&#8217;ve dipped our toes in this pool before (icon contest, graphic design component for Trac tickets, header refresh contest, etc.), but this year we&#8217;re going to cannonball and make a big splash. Here&#8217;s what you need to know if you want to get involved.</p>
<p><strong>A list for all seasons. </strong>Developers have the <a href="http://lists.automattic.com/mailman/listinfo/wp-hackers">wp-hackers mailing list</a> to discuss core and plugin code. Sometimes UI/UX stuff comes up and gets discussed there, but there is a whole universe of discussion around navigation labels, gradients, button styling, layouts, alignment, etc. that would be clutter on wp-hackers. Designers need a list to call their own, and now we have one. You can sign up for the <a href="http://lists.automattic.com/mailman/listinfo/wp-ui">wp-ui list</a> to discuss ways to improve the interface or user experience of WordPress, and to discuss progress on design-related projects for the open source project, like the design challenges we&#8217;re going to have.</p>
<p><strong>Design Challenges.</strong> We learned a lot from the icon design and header refresh contests, and we want to do these kind of open design challenges on a regular basis to give UI/UX designers who want to contribute to the WordPress open source project more opportunities to do so. If we could do one per month, that would be ideal, keeping the challenges relatively bite-sized to allow potential contributors an easy way to get involved at first. As each challenge is posted, people can use the list to bounce ideas off each other and work toward optimal solutions. I&#8217;m hoping the design challenges will evolve to be less contest and more collaboration. We&#8217;ll announce the first one before the end of January, so if you&#8217;re interested, please sign up for the list! <em>(Hint: one will likely be a touch up to the Right Now dashboard module, to improve the information design, and there will be a couple of screen layout challenges coming up as well.)</em></p>
<p><strong>Distributed Usability Testing.</strong><em> </em>We started to try this out last year, and several dozen usability professionals volunteered to help get the program going, but a combination of scheduling and infrastructure issues combined to stall the progress. Having the &#8220;UI/UX contributor team&#8221; infrastructure in place, starting with the mailing list, will make it much easier to get this project going again.</p>
<p><strong>Chit-chat.</strong> The weekly developer chats in IRC at <a href="https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev">#wordpress-dev</a> have been very productive. We&#8217;ve created an IRC room at <a href="http://webchat.freenode.net/?channels=wordpress-ui">#wordpress-ui on irc.freenode.net</a> so that we can have the same kind of &#8220;water cooler&#8221; for UI/UX contributors as for core code contributors. In addition to being a place where you can drop in and discuss core UI/UX (note: this room will not be a place to discuss the design of blog themes, it&#8217;s to discuss the design of the Wordpress application itself), we&#8217;ll set up a weekly chat. Choosing a day and time for the chats will probably be the first discussion on the mailing list.</p>
<p><strong>A blog of our own. </strong>Once again, taking a page from the code contributor infrastructure, we&#8217;ll set up a blog for UI/UX updates, announcements, progress reports, etc. This will be on WordPress.org in the nearish future, and will be announced to the mailing list when it is live.</p>
<p>So, if you want to become a contributor to core WordPress by using your design skills, <a href="http://lists.automattic.com/mailman/listinfo/wp-ui">join the wp-ui mailing list</a> and get ready for a fun year!</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:70:"http://wordpress.org/development/2010/01/2010-open-source-design/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"3";}s:7:"summary";s:332:"2010 is the year we dive into open source design. We&#8217;ve dipped our toes in this pool before (icon contest, graphic design component for Trac tickets, header refresh contest, etc.), but this year we&#8217;re going to cannonball and make a big splash. Here&#8217;s what you need to know if you want to get involved.
A list [...]";s:12:"atom_content";s:3855:"<p>2010 is the year we dive into open source design. We&#8217;ve dipped our toes in this pool before (icon contest, graphic design component for Trac tickets, header refresh contest, etc.), but this year we&#8217;re going to cannonball and make a big splash. Here&#8217;s what you need to know if you want to get involved.</p>
<p><strong>A list for all seasons. </strong>Developers have the <a href="http://lists.automattic.com/mailman/listinfo/wp-hackers">wp-hackers mailing list</a> to discuss core and plugin code. Sometimes UI/UX stuff comes up and gets discussed there, but there is a whole universe of discussion around navigation labels, gradients, button styling, layouts, alignment, etc. that would be clutter on wp-hackers. Designers need a list to call their own, and now we have one. You can sign up for the <a href="http://lists.automattic.com/mailman/listinfo/wp-ui">wp-ui list</a> to discuss ways to improve the interface or user experience of WordPress, and to discuss progress on design-related projects for the open source project, like the design challenges we&#8217;re going to have.</p>
<p><strong>Design Challenges.</strong> We learned a lot from the icon design and header refresh contests, and we want to do these kind of open design challenges on a regular basis to give UI/UX designers who want to contribute to the WordPress open source project more opportunities to do so. If we could do one per month, that would be ideal, keeping the challenges relatively bite-sized to allow potential contributors an easy way to get involved at first. As each challenge is posted, people can use the list to bounce ideas off each other and work toward optimal solutions. I&#8217;m hoping the design challenges will evolve to be less contest and more collaboration. We&#8217;ll announce the first one before the end of January, so if you&#8217;re interested, please sign up for the list! <em>(Hint: one will likely be a touch up to the Right Now dashboard module, to improve the information design, and there will be a couple of screen layout challenges coming up as well.)</em></p>
<p><strong>Distributed Usability Testing.</strong><em> </em>We started to try this out last year, and several dozen usability professionals volunteered to help get the program going, but a combination of scheduling and infrastructure issues combined to stall the progress. Having the &#8220;UI/UX contributor team&#8221; infrastructure in place, starting with the mailing list, will make it much easier to get this project going again.</p>
<p><strong>Chit-chat.</strong> The weekly developer chats in IRC at <a href="https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev">#wordpress-dev</a> have been very productive. We&#8217;ve created an IRC room at <a href="http://webchat.freenode.net/?channels=wordpress-ui">#wordpress-ui on irc.freenode.net</a> so that we can have the same kind of &#8220;water cooler&#8221; for UI/UX contributors as for core code contributors. In addition to being a place where you can drop in and discuss core UI/UX (note: this room will not be a place to discuss the design of blog themes, it&#8217;s to discuss the design of the Wordpress application itself), we&#8217;ll set up a weekly chat. Choosing a day and time for the chats will probably be the first discussion on the mailing list.</p>
<p><strong>A blog of our own. </strong>Once again, taking a page from the code contributor infrastructure, we&#8217;ll set up a blog for UI/UX updates, announcements, progress reports, etc. This will be on WordPress.org in the nearish future, and will be announced to the mailing list when it is live.</p>
<p>So, if you want to become a contributor to core WordPress by using your design skills, <a href="http://lists.automattic.com/mailman/listinfo/wp-ui">join the wp-ui mailing list</a> and get ready for a fun year!</p>
";}i:2;a:13:{s:5:"title";s:15:"WordPress 2.9.1";s:4:"link";s:57:"http://wordpress.org/development/2010/01/wordpress-2-9-1/";s:8:"comments";s:66:"http://wordpress.org/development/2010/01/wordpress-2-9-1/#comments";s:7:"pubdate";s:31:"Mon, 04 Jan 2010 22:35:31 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:40:"http://wordpress.org/development/?p=1140";s:11:"description";s:351:"After over a million downloads of WordPress 2.9 and lots of feedback from all of you, we&#8217;re releasing WordPress  2.9.1.  This release addresses a handful of minor issues as well as a rather annoying problem where scheduled posts and pingbacks are not processed correctly due to incompatibilities with some hosts.  If any of these issues [...]";s:7:"content";a:1:{s:7:"encoded";s:681:"<p>After over a million downloads of WordPress 2.9 and lots of feedback from all of you, we&#8217;re releasing WordPress  2.9.1.  This release addresses a handful of minor issues as well as a rather annoying problem where scheduled posts and pingbacks are not processed correctly due to incompatibilities with some hosts.  If any of <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">these issues</a> affect you, give 2.9.1 a try.  <a href="http://wordpress.org/download/">Download 2.9.1</a> or upgrade automatically from the Tools-&gt;Upgrade menu in your blog&#8217;s admin area.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:62:"http://wordpress.org/development/2010/01/wordpress-2-9-1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:351:"After over a million downloads of WordPress 2.9 and lots of feedback from all of you, we&#8217;re releasing WordPress  2.9.1.  This release addresses a handful of minor issues as well as a rather annoying problem where scheduled posts and pingbacks are not processed correctly due to incompatibilities with some hosts.  If any of these issues [...]";s:12:"atom_content";s:681:"<p>After over a million downloads of WordPress 2.9 and lots of feedback from all of you, we&#8217;re releasing WordPress  2.9.1.  This release addresses a handful of minor issues as well as a rather annoying problem where scheduled posts and pingbacks are not processed correctly due to incompatibilities with some hosts.  If any of <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">these issues</a> affect you, give 2.9.1 a try.  <a href="http://wordpress.org/download/">Download 2.9.1</a> or upgrade automatically from the Tools-&gt;Upgrade menu in your blog&#8217;s admin area.</p>
";}i:3;a:13:{s:5:"title";s:20:"Early 2010 WordCamps";s:4:"link";s:62:"http://wordpress.org/development/2010/01/early-2010-wordcamps/";s:8:"comments";s:71:"http://wordpress.org/development/2010/01/early-2010-wordcamps/#comments";s:7:"pubdate";s:31:"Mon, 04 Jan 2010 19:40:48 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:8:"WordCamp";s:4:"guid";s:40:"http://wordpress.org/development/?p=1127";s:11:"description";s:297:"Rested up from the holidays? I hope so, because the new year has begun and a lot is going to be happening with WordPress in 2010, and you definitely want to be a part of it. Later this week the scope for version 3.0 (featuring the addition of MU functionality to the WordPress codebase) will [...]";s:7:"content";a:1:{s:7:"encoded";s:8301:"<p>Rested up from the holidays? I hope so, because the new year has begun and <strong>a lot </strong>is going to be happening with WordPress in 2010, and you definitely want to be a part of it. Later this week the scope for version 3.0 (featuring the addition of MU functionality to the WordPress codebase) will be decided in the IRC developer chat*, based on <a href="http://wordpress.org/support/topic/345127">feedback provided by users like you</a>. But it&#8217;s no fun to live by IRC alone, which is why we love WordCamps. Attending a WordCamp gives you a chance to meet people in your local community who are working with WordPress, as well as core contributors, theme designers, plugin developers, Codex writers, support forum moderators and other WordPress volunteers who&#8217;ve made WordPress what it is today. Add this New Year&#8217;s Resolution to your 2010 list if it&#8217;s not on there already: Attend a WordCamp, meet at least 5 new local people, learn something new, and if you have the chance, buy a drink for someone who&#8217;s volunteered their time and expertise to the WordPress open source project. To help you keep your resolution, here is a list of the upcoming WordCamps for the next three months, followed by what I know so far about each one.</p>
<p>January 8–9: <a href="http://atlantawordcamp.com/">WordCamp Atlanta</a><br />
January 23: <a href="http://wordcampboston.com/">WordCamp Boston</a><br />
January 30: <a href="http://www.wordcamp.gr/">WordCamp Greece</a> in Thessaloniki<br />
January 30: <a href="http://id.wordcamp.org/">WordCamp Indonesia</a> in Jakarta<br />
February 27: <a href="http://2010.wordcampfukuoka.com/">WordCamp Fukuoka</a><br />
March 6–7: <a href="http://www.wordcampireland.com/">WordCamp Ireland</a> in Kilkenny<br />
March 27–28: <a href="http://wordcamptoronto.com/">WordCamp Toronto</a></p>
<h4>NORTH AMERICA</h4>
<p><strong>January 8–9: <a href="http://atlantawordcamp.com/">WordCamp Atlanta</a>.</strong> First WordCamp of the year, and it&#8217;s already sold out &#8212; twice! They changed to a bigger venue based on demand, from Georgia Tech to the Atlanta campus of Savannah College of Art and Design (SCAD). They&#8217;re still letting people onto <a href="http://wordcampatl.eventbrite.com/">the waitlist</a>, if you&#8217;re interested. A guaranteed way to get in would be to <a href="http://atlantawordcamp.com/sponsor/sponsorship-opportunities/">sponsor</a> the event, and they&#8217;re taking last-minute sponsors right now. Atlanta will have sessions on Friday evening and all day Saturday. I&#8217;ll be opening the Saturday program with <em>WordPress Resolutions: What to Expect in 2010</em>. After a day of design, development and content track sessions, Lead Developer <a href="http://markjaquith.com/">Mark Jaquith</a> will take the closing slot for a Town Hall-style Q&amp;A.  The <a href="http://wordcampatl.eventbrite.com/">attendee list</a> (follow link, scroll down) includes a number of WordPress core contributors, theme/plugin developers, and support providers as well as proof that Atlanta has a strong WordPress user base.</p>
<p><strong>January 23: <a href="http://wordcampboston.com/">WordCamp Boston</a>.</strong> I think WordCamp Boston is trying to one-up every WordCamp the organizers have been to, including the awesome NYC from November, and it looks like they might succeed. From <a href="http://blogs.law.harvard.edu/doc/">Doc Searls</a> and <a href="http://www.hyperorg.com/blogger/">David Weinberger</a> as keynote speakers to the multiple-track, unconference and Ignite sessions to the sweet-looking venue and the party plans, this one has got it going on. I credit it in part to the fact that they are one of the few WordCamps to follow the advice of having an organizing team of more than just 2 or 3 people, so the work is better distributed. I see a number of familiar names on the <a href="http://wordcampboston.com/registration/attendees/">attendee list</a>, but even more that I don&#8217;t know, so I&#8217;m looking forward to meeting the Boston WordPress community. They&#8217;re still <a href="http://wordcampboston.com/registration/">selling tickets</a>, so if you&#8217;re in the northeast, you should try to make it. I&#8217;ll be at this one also, talking about how the merge with MU will affect the WordPress admin (by then we should have started figuring it out!).</p>
<p><strong>March 27–28: <a href="http://wordcamptoronto.com/">WordCamp Toronto</a>.</strong> The last two Toronto WordCamps have been really good. I heard there would be one in March, but their site right now is just <a href="http://wordcamptoronto.com/">taking emails</a> for notification. I&#8217;ve contacted the organizer to see what&#8217;s up, and he says the site will likely go live this week. They&#8217;re looking for volunteers to help organize this year&#8217;s event, so if you&#8217;re interested, it would be a great opportunity to get involved. Believe me, volunteering at a WordCamp is one of the best ways to make sure you meet a lot of other attendees.</p>
<h4>ASIA</h4>
<p><strong>January 30: <a href="http://id.wordcamp.org/">WordCamp Indonesia</a>.</strong> WordCamp Indonesia will be in Jakarta again this year. I love how they worded the beginning of their <a href="http://id.wordcamp.org/conference-sessions/">sessions</a> page. &#8220;Come in, we’ll get you breakfast and coffee, you’ll register, there’ll be networking. It’ll be great.&#8221; There will be a single track of sessions, but there are several time slots set aside for ad-hoc discussion and breakout sessions.</p>
<p><strong>February 27: <a href="http://2010.wordcampfukuoka.com/">WordCamp Fukuoka</a>.</strong> WordCamp Fukuoka is just getting its site up, too, so check back periodically a little later for more information. One of their visiting speakers will be <a href="http://noel.io/">Noel Jackson</a>, developer of the <a href="http://codex.wordpress.org/Press_This">Press This</a> bookmarklet as well as themes like <a href="http://wordpress.org/extend/themes/p2">P2</a> and <a href="http://wordpress.org/extend/themes/monotone">Monotone</a>/<a href="http://wordpress.org/extend/themes/duotone">Duotone</a>.</p>
<h4>EUROPE</h4>
<p><strong>January 30: <a href="http://www.wordcamp.gr/">WordCamp Greece</a>.</strong> WordCamp Greece will be held in Thessaloniki, and they expect about 100-150 people to attend.The program includes regular sessions on the usual topics (how-to, programming, SEO, multi-language sites, etc) as well as &#8220;QuickRounds,&#8221; which will showcase Greek projects based on WordPress. I&#8217;m especially intrigued by the &#8220;WordPress vs. Expression Engine&#8221; session. Whenever people compare different publishing platforms, it&#8217;s interesting to see which features they highlight. I hope someone gets video from this one and posts it to the <a href="http://wordpress.tv/category/wordcamptv/">WordCamp section of WordPress.tv</a>.</p>
<p><strong>March 6–7: <a href="http://www.wordcampireland.com/">WordCamp Ireland</a>.</strong> WordCamp Ireland will be in Kilkenny, and for such a geographically small country, it&#8217;s got an impressive list of <a href="http://www.wordcampireland.com/info/speakers/">speakers</a>, including <a href="http://ocaoimh.ie/">Donncha O Caoimh</a>, lead developer of <a href="http://mu.wordpress.org/">WordPress MU</a>. The program includes three tracks: Intro, Blogger, and Developer, and I think this will be the first WordCamp I&#8217;ve heard of that is deliberately <a href="http://www.wordcampireland.com/about/family-and-partner-friendly/">family-friendly</a>, with on-site child care. They&#8217;re also going to have a charging station for mobile devices, which is clever. It&#8217;s not confirmed yet, but I think I&#8217;ll be at this one, too.</p>
<p>If you want to attend a WordCamp but don&#8217;t know of one near you, check out <a href="http://central.wordcamp.org/">WordCamp.org</a> for the official list (updated frequently). That&#8217;s also where you would start if you wanted to <a href="http://central.wordcamp.org/guidelines/">organize a WordCamp</a> in your area. </p>
<p><em>*Developer chats are held Thursdays at 21:00 UTC in the #wordpress-dev channel at irc.freenode.com. </em></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:67:"http://wordpress.org/development/2010/01/early-2010-wordcamps/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:297:"Rested up from the holidays? I hope so, because the new year has begun and a lot is going to be happening with WordPress in 2010, and you definitely want to be a part of it. Later this week the scope for version 3.0 (featuring the addition of MU functionality to the WordPress codebase) will [...]";s:12:"atom_content";s:8301:"<p>Rested up from the holidays? I hope so, because the new year has begun and <strong>a lot </strong>is going to be happening with WordPress in 2010, and you definitely want to be a part of it. Later this week the scope for version 3.0 (featuring the addition of MU functionality to the WordPress codebase) will be decided in the IRC developer chat*, based on <a href="http://wordpress.org/support/topic/345127">feedback provided by users like you</a>. But it&#8217;s no fun to live by IRC alone, which is why we love WordCamps. Attending a WordCamp gives you a chance to meet people in your local community who are working with WordPress, as well as core contributors, theme designers, plugin developers, Codex writers, support forum moderators and other WordPress volunteers who&#8217;ve made WordPress what it is today. Add this New Year&#8217;s Resolution to your 2010 list if it&#8217;s not on there already: Attend a WordCamp, meet at least 5 new local people, learn something new, and if you have the chance, buy a drink for someone who&#8217;s volunteered their time and expertise to the WordPress open source project. To help you keep your resolution, here is a list of the upcoming WordCamps for the next three months, followed by what I know so far about each one.</p>
<p>January 8–9: <a href="http://atlantawordcamp.com/">WordCamp Atlanta</a><br />
January 23: <a href="http://wordcampboston.com/">WordCamp Boston</a><br />
January 30: <a href="http://www.wordcamp.gr/">WordCamp Greece</a> in Thessaloniki<br />
January 30: <a href="http://id.wordcamp.org/">WordCamp Indonesia</a> in Jakarta<br />
February 27: <a href="http://2010.wordcampfukuoka.com/">WordCamp Fukuoka</a><br />
March 6–7: <a href="http://www.wordcampireland.com/">WordCamp Ireland</a> in Kilkenny<br />
March 27–28: <a href="http://wordcamptoronto.com/">WordCamp Toronto</a></p>
<h4>NORTH AMERICA</h4>
<p><strong>January 8–9: <a href="http://atlantawordcamp.com/">WordCamp Atlanta</a>.</strong> First WordCamp of the year, and it&#8217;s already sold out &#8212; twice! They changed to a bigger venue based on demand, from Georgia Tech to the Atlanta campus of Savannah College of Art and Design (SCAD). They&#8217;re still letting people onto <a href="http://wordcampatl.eventbrite.com/">the waitlist</a>, if you&#8217;re interested. A guaranteed way to get in would be to <a href="http://atlantawordcamp.com/sponsor/sponsorship-opportunities/">sponsor</a> the event, and they&#8217;re taking last-minute sponsors right now. Atlanta will have sessions on Friday evening and all day Saturday. I&#8217;ll be opening the Saturday program with <em>WordPress Resolutions: What to Expect in 2010</em>. After a day of design, development and content track sessions, Lead Developer <a href="http://markjaquith.com/">Mark Jaquith</a> will take the closing slot for a Town Hall-style Q&amp;A.  The <a href="http://wordcampatl.eventbrite.com/">attendee list</a> (follow link, scroll down) includes a number of WordPress core contributors, theme/plugin developers, and support providers as well as proof that Atlanta has a strong WordPress user base.</p>
<p><strong>January 23: <a href="http://wordcampboston.com/">WordCamp Boston</a>.</strong> I think WordCamp Boston is trying to one-up every WordCamp the organizers have been to, including the awesome NYC from November, and it looks like they might succeed. From <a href="http://blogs.law.harvard.edu/doc/">Doc Searls</a> and <a href="http://www.hyperorg.com/blogger/">David Weinberger</a> as keynote speakers to the multiple-track, unconference and Ignite sessions to the sweet-looking venue and the party plans, this one has got it going on. I credit it in part to the fact that they are one of the few WordCamps to follow the advice of having an organizing team of more than just 2 or 3 people, so the work is better distributed. I see a number of familiar names on the <a href="http://wordcampboston.com/registration/attendees/">attendee list</a>, but even more that I don&#8217;t know, so I&#8217;m looking forward to meeting the Boston WordPress community. They&#8217;re still <a href="http://wordcampboston.com/registration/">selling tickets</a>, so if you&#8217;re in the northeast, you should try to make it. I&#8217;ll be at this one also, talking about how the merge with MU will affect the WordPress admin (by then we should have started figuring it out!).</p>
<p><strong>March 27–28: <a href="http://wordcamptoronto.com/">WordCamp Toronto</a>.</strong> The last two Toronto WordCamps have been really good. I heard there would be one in March, but their site right now is just <a href="http://wordcamptoronto.com/">taking emails</a> for notification. I&#8217;ve contacted the organizer to see what&#8217;s up, and he says the site will likely go live this week. They&#8217;re looking for volunteers to help organize this year&#8217;s event, so if you&#8217;re interested, it would be a great opportunity to get involved. Believe me, volunteering at a WordCamp is one of the best ways to make sure you meet a lot of other attendees.</p>
<h4>ASIA</h4>
<p><strong>January 30: <a href="http://id.wordcamp.org/">WordCamp Indonesia</a>.</strong> WordCamp Indonesia will be in Jakarta again this year. I love how they worded the beginning of their <a href="http://id.wordcamp.org/conference-sessions/">sessions</a> page. &#8220;Come in, we’ll get you breakfast and coffee, you’ll register, there’ll be networking. It’ll be great.&#8221; There will be a single track of sessions, but there are several time slots set aside for ad-hoc discussion and breakout sessions.</p>
<p><strong>February 27: <a href="http://2010.wordcampfukuoka.com/">WordCamp Fukuoka</a>.</strong> WordCamp Fukuoka is just getting its site up, too, so check back periodically a little later for more information. One of their visiting speakers will be <a href="http://noel.io/">Noel Jackson</a>, developer of the <a href="http://codex.wordpress.org/Press_This">Press This</a> bookmarklet as well as themes like <a href="http://wordpress.org/extend/themes/p2">P2</a> and <a href="http://wordpress.org/extend/themes/monotone">Monotone</a>/<a href="http://wordpress.org/extend/themes/duotone">Duotone</a>.</p>
<h4>EUROPE</h4>
<p><strong>January 30: <a href="http://www.wordcamp.gr/">WordCamp Greece</a>.</strong> WordCamp Greece will be held in Thessaloniki, and they expect about 100-150 people to attend.The program includes regular sessions on the usual topics (how-to, programming, SEO, multi-language sites, etc) as well as &#8220;QuickRounds,&#8221; which will showcase Greek projects based on WordPress. I&#8217;m especially intrigued by the &#8220;WordPress vs. Expression Engine&#8221; session. Whenever people compare different publishing platforms, it&#8217;s interesting to see which features they highlight. I hope someone gets video from this one and posts it to the <a href="http://wordpress.tv/category/wordcamptv/">WordCamp section of WordPress.tv</a>.</p>
<p><strong>March 6–7: <a href="http://www.wordcampireland.com/">WordCamp Ireland</a>.</strong> WordCamp Ireland will be in Kilkenny, and for such a geographically small country, it&#8217;s got an impressive list of <a href="http://www.wordcampireland.com/info/speakers/">speakers</a>, including <a href="http://ocaoimh.ie/">Donncha O Caoimh</a>, lead developer of <a href="http://mu.wordpress.org/">WordPress MU</a>. The program includes three tracks: Intro, Blogger, and Developer, and I think this will be the first WordCamp I&#8217;ve heard of that is deliberately <a href="http://www.wordcampireland.com/about/family-and-partner-friendly/">family-friendly</a>, with on-site child care. They&#8217;re also going to have a charging station for mobile devices, which is clever. It&#8217;s not confirmed yet, but I think I&#8217;ll be at this one, too.</p>
<p>If you want to attend a WordCamp but don&#8217;t know of one near you, check out <a href="http://central.wordcamp.org/">WordCamp.org</a> for the official list (updated frequently). That&#8217;s also where you would start if you wanted to <a href="http://central.wordcamp.org/guidelines/">organize a WordCamp</a> in your area. </p>
<p><em>*Developer chats are held Thursdays at 21:00 UTC in the #wordpress-dev channel at irc.freenode.com. </em></p>
";}i:4;a:13:{s:5:"title";s:35:"WordPress 2.9.1 Release Candidate 1";s:4:"link";s:77:"http://wordpress.org/development/2009/12/wordpress-2-9-1-release-candidate-1/";s:8:"comments";s:86:"http://wordpress.org/development/2009/12/wordpress-2-9-1-release-candidate-1/#comments";s:7:"pubdate";s:31:"Tue, 29 Dec 2009 23:27:23 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:19:"DevelopmentReleases";s:4:"guid";s:40:"http://wordpress.org/development/?p=1119";s:11:"description";s:334:"Thanks to everyone who tested 2.9.1 Beta 1.  We&#8217;re following that up with Release Candidate 1.  RC1 contains a few more fixes, bringing the number of fixed tickets up to 23.  If you are already running Beta 1, visit Tools-&#62;Upgrade in your blog&#8217;s admin to get RC1.  You can also  download the RC1 package and [...]";s:7:"content";a:1:{s:7:"encoded";s:682:"<p>Thanks to everyone who tested <a href="http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/">2.9.1 Beta 1</a>.  We&#8217;re following that up with Release Candidate 1.  RC1 contains a few more fixes, bringing the number of <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">fixed tickets</a> up to 23.  If you are already running Beta 1, visit Tools-&gt;Upgrade in your blog&#8217;s admin to get RC1.  You can also  <a href="http://wordpress.org/wordpress-2.9.1-RC1.zip">download the RC1 package</a> and install manually.  If all goes well, 2.9.1 will be here soon.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:82:"http://wordpress.org/development/2009/12/wordpress-2-9-1-release-candidate-1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"1";}s:7:"summary";s:334:"Thanks to everyone who tested 2.9.1 Beta 1.  We&#8217;re following that up with Release Candidate 1.  RC1 contains a few more fixes, bringing the number of fixed tickets up to 23.  If you are already running Beta 1, visit Tools-&#62;Upgrade in your blog&#8217;s admin to get RC1.  You can also  download the RC1 package and [...]";s:12:"atom_content";s:682:"<p>Thanks to everyone who tested <a href="http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/">2.9.1 Beta 1</a>.  We&#8217;re following that up with Release Candidate 1.  RC1 contains a few more fixes, bringing the number of <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">fixed tickets</a> up to 23.  If you are already running Beta 1, visit Tools-&gt;Upgrade in your blog&#8217;s admin to get RC1.  You can also  <a href="http://wordpress.org/wordpress-2.9.1-RC1.zip">download the RC1 package</a> and install manually.  If all goes well, 2.9.1 will be here soon.</p>
";}i:5;a:13:{s:5:"title";s:13:"Setting Scope";s:4:"link";s:55:"http://wordpress.org/development/2009/12/setting-scope/";s:8:"comments";s:64:"http://wordpress.org/development/2009/12/setting-scope/#comments";s:7:"pubdate";s:31:"Fri, 25 Dec 2009 16:56:38 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:11:"Development";s:4:"guid";s:40:"http://wordpress.org/development/?p=1096";s:11:"description";s:301:"Merry Christmas! One of the things that was discussed at the core commit team meetup was release scope (and scope creep). Now that 2.9 is out and it&#8217;s time to start thinking about 3.0, we think it would be appropriate to stop and take a breath before diving in, and make a plan in advance. [...]";s:7:"content";a:1:{s:7:"encoded";s:4722:"<p>Merry Christmas! One of the things that was discussed at the core commit team meetup was release scope (and scope creep). Now that 2.9 is out and it&#8217;s time to start thinking about 3.0, we think it would be appropriate to stop and take a breath before diving in, and make a plan in advance. What winds up happening is that during each release cycle a few new features are selected for inclusion, but then right up until feature freeze (and/or beta cycle), people keep adding feature requests, patches for enhancements, and ongoing bug reports. This means each release winds up getting pushed out later than planned, and with so many things going in per release, it becomes harder to catch new bugs.</p>
<p>The as-long-as-we&#8217;re-not-in-freeze-yet model isn&#8217;t working. People wind up waiting months longer for new features they want, like Trash and Image Editing, because we&#8217;re still adding other things and then we need to test them all. If we kept the releases smaller feature-wise, we could push out the new stuff sooner (3 releases per year is the goal) and have more focused beta testing, making the releases themselves better. It&#8217;s hard, because everyone has their pet features and fixes, and if there&#8217;s a patch, why not get it in this release rather than waiting? Sometimes people complain that a patch has been waiting to be committed for weeks or months, but what no one ever seems to bring up is that sometimes patches introduce new bugs, and the more we add at once, the harder it is to keep it all well-tested on various platforms, in different hosting environments, etc. So. What&#8217;s our proposal?</p>
<p>We take a page from the world of project management and we make a project plan <strong>before</strong> we jump into the dev cycle. We let everyone propose features and enhancements, and we choose a limited number to include in 3.0 (in this case we need to be especially stringent, because the merge of WordPress and WordPress MU will automatically mean a lot of work) and set a realistic release date that we stick to. We create a tentative set of features for the next two releases, to be re-evaluated at the beginning of the next cycle, so that people know the community is committed to certain features, as opposed to the vague &#8220;future release&#8221; label we now use for everything not included in the current version. We fix bugs that are reproducible and affect a large number of users before focusing on edge case bugs or bugs that haven&#8217;t been well-described or reproduced. We stop diverting our attention from agreed-upon goals when a &#8220;squeaky wheel&#8221; decides we should all be focused on something else. There are always things that pop up unexpectedly, but we need to do a better job of restraining ourselves when it comes to trying to sneak things into the current release (I include myself in this, of course&#8230;as a UX person I always wish we could do everything all at once!).</p>
<p>As an open source project, we accomplish more when we work together than we do following individual agendas, and we need to keep our project focused on commonly-agreed-upon goals instead of following tangents whenever a community member starts to take us on one, regardless of whether it&#8217;s to follow a cool idea that everyone loves or a suggestion based on a personal agenda, and regardless of whether it&#8217;s a newbie who doesn&#8217;t know any better or a frequent contributor or committer who has a strong opinion and a loud voice (so to speak). The issue here is that it&#8217;s easy to get distracted, so we need to create a structure that will help us keep moving forward instead of getting sidetracked. We need to keep Trac clean for the current dev cycle so that it includes confirmed features and bug reports, and all new feature suggestions go into a different milestone.</p>
<p>We think it&#8217;s at least worth a try. When we re-start the weekly IRC dev chats in 2010, the first meeting will be to talk about the scope of 3.0. When we&#8217;ve got a general agreement about what will be included, we&#8217;ll create the appropriate Trac tickets, and punt tickets for non-3.0 feature requests/enhancements to a future release so we can stay focused. New bug reports will still come in to the current milestone. It&#8217;s going to be hard. There are at least a dozen new features that I feel like we&#8217;ve pushed back multiple times that I&#8217;d like to see in core, but for this experiment, I&#8217;m just going to keep reminding myself, &#8220;You can do that with a plugin!&#8221;</p>
<p><a href="http://wordpress.org/support/topic/345127">Sound off on the features you would like to see in version 3.0</a>.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2009/12/setting-scope/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"6";}s:7:"summary";s:301:"Merry Christmas! One of the things that was discussed at the core commit team meetup was release scope (and scope creep). Now that 2.9 is out and it&#8217;s time to start thinking about 3.0, we think it would be appropriate to stop and take a breath before diving in, and make a plan in advance. [...]";s:12:"atom_content";s:4722:"<p>Merry Christmas! One of the things that was discussed at the core commit team meetup was release scope (and scope creep). Now that 2.9 is out and it&#8217;s time to start thinking about 3.0, we think it would be appropriate to stop and take a breath before diving in, and make a plan in advance. What winds up happening is that during each release cycle a few new features are selected for inclusion, but then right up until feature freeze (and/or beta cycle), people keep adding feature requests, patches for enhancements, and ongoing bug reports. This means each release winds up getting pushed out later than planned, and with so many things going in per release, it becomes harder to catch new bugs.</p>
<p>The as-long-as-we&#8217;re-not-in-freeze-yet model isn&#8217;t working. People wind up waiting months longer for new features they want, like Trash and Image Editing, because we&#8217;re still adding other things and then we need to test them all. If we kept the releases smaller feature-wise, we could push out the new stuff sooner (3 releases per year is the goal) and have more focused beta testing, making the releases themselves better. It&#8217;s hard, because everyone has their pet features and fixes, and if there&#8217;s a patch, why not get it in this release rather than waiting? Sometimes people complain that a patch has been waiting to be committed for weeks or months, but what no one ever seems to bring up is that sometimes patches introduce new bugs, and the more we add at once, the harder it is to keep it all well-tested on various platforms, in different hosting environments, etc. So. What&#8217;s our proposal?</p>
<p>We take a page from the world of project management and we make a project plan <strong>before</strong> we jump into the dev cycle. We let everyone propose features and enhancements, and we choose a limited number to include in 3.0 (in this case we need to be especially stringent, because the merge of WordPress and WordPress MU will automatically mean a lot of work) and set a realistic release date that we stick to. We create a tentative set of features for the next two releases, to be re-evaluated at the beginning of the next cycle, so that people know the community is committed to certain features, as opposed to the vague &#8220;future release&#8221; label we now use for everything not included in the current version. We fix bugs that are reproducible and affect a large number of users before focusing on edge case bugs or bugs that haven&#8217;t been well-described or reproduced. We stop diverting our attention from agreed-upon goals when a &#8220;squeaky wheel&#8221; decides we should all be focused on something else. There are always things that pop up unexpectedly, but we need to do a better job of restraining ourselves when it comes to trying to sneak things into the current release (I include myself in this, of course&#8230;as a UX person I always wish we could do everything all at once!).</p>
<p>As an open source project, we accomplish more when we work together than we do following individual agendas, and we need to keep our project focused on commonly-agreed-upon goals instead of following tangents whenever a community member starts to take us on one, regardless of whether it&#8217;s to follow a cool idea that everyone loves or a suggestion based on a personal agenda, and regardless of whether it&#8217;s a newbie who doesn&#8217;t know any better or a frequent contributor or committer who has a strong opinion and a loud voice (so to speak). The issue here is that it&#8217;s easy to get distracted, so we need to create a structure that will help us keep moving forward instead of getting sidetracked. We need to keep Trac clean for the current dev cycle so that it includes confirmed features and bug reports, and all new feature suggestions go into a different milestone.</p>
<p>We think it&#8217;s at least worth a try. When we re-start the weekly IRC dev chats in 2010, the first meeting will be to talk about the scope of 3.0. When we&#8217;ve got a general agreement about what will be included, we&#8217;ll create the appropriate Trac tickets, and punt tickets for non-3.0 feature requests/enhancements to a future release so we can stay focused. New bug reports will still come in to the current milestone. It&#8217;s going to be hard. There are at least a dozen new features that I feel like we&#8217;ve pushed back multiple times that I&#8217;d like to see in core, but for this experiment, I&#8217;m just going to keep reminding myself, &#8220;You can do that with a plugin!&#8221;</p>
<p><a href="http://wordpress.org/support/topic/345127">Sound off on the features you would like to see in version 3.0</a>.</p>
";}i:6;a:13:{s:5:"title";s:22:"WordPress 2.9.1 Beta 1";s:4:"link";s:64:"http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/";s:8:"comments";s:73:"http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/#comments";s:7:"pubdate";s:31:"Wed, 23 Dec 2009 19:58:34 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:40:"http://wordpress.org/development/?p=1098";s:11:"description";s:354:"Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP&#8217;s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help [...]";s:7:"content";a:1:{s:7:"encoded";s:1162:"<p>Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP&#8217;s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help us get 2.9.1 ready to go by testing 2.9.1 Beta 1.  The easiest way to test Beta 1 is to install the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin, elect to get on the point release development track, and then perform an automatic upgrade via the Tools-&gt;Upgrade menu.  You can also <a href="http://wordpress.org/wordpress-2.9.1-beta1.zip">download the Beta 1 package</a> and install manually.  <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">Fourteen tickets</a> have been fixed in 2.9.1 Beta 1.  Since the curl problem and a couple of other problems are dependent on specific hosting configurations, any and all testing help is greatly appreciated.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:69:"http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"1";}s:7:"summary";s:354:"Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP&#8217;s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help [...]";s:12:"atom_content";s:1162:"<p>Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP&#8217;s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help us get 2.9.1 ready to go by testing 2.9.1 Beta 1.  The easiest way to test Beta 1 is to install the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin, elect to get on the point release development track, and then perform an automatic upgrade via the Tools-&gt;Upgrade menu.  You can also <a href="http://wordpress.org/wordpress-2.9.1-beta1.zip">download the Beta 1 package</a> and install manually.  <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">Fourteen tickets</a> have been fixed in 2.9.1 Beta 1.  Since the curl problem and a couple of other problems are dependent on specific hosting configurations, any and all testing help is greatly appreciated.</p>
";}i:7;a:13:{s:5:"title";s:25:"WordPress 2.9, oh so fine";s:4:"link";s:55:"http://wordpress.org/development/2009/12/wordpress-2-9/";s:8:"comments";s:64:"http://wordpress.org/development/2009/12/wordpress-2-9/#comments";s:7:"pubdate";s:31:"Sat, 19 Dec 2009 00:46:11 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:8:"Releases";s:4:"guid";s:40:"http://wordpress.org/development/?p=1075";s:11:"description";s:360:"I want to make you mine, all the time&#8230; oh wait. Hello. I&#8217;m here on behalf of the entire WordPress development team and community to announce the immediate availability of WordPress version 2.9 &#8220;Carmen&#8221; named in honor of magical jazz vocalist Carmen McRae (whom we&#8217;ve added to our Last.fm WP release station). You can upgrade [...]";s:7:"content";a:1:{s:7:"encoded";s:14105:"<p>I want to make you mine, all the time&#8230; oh wait. Hello. I&#8217;m here on behalf of the entire WordPress development team and community to announce the immediate availability of <a href="http://wordpress.org/download/">WordPress version 2.9 &#8220;Carmen&#8221;</a> named in honor of magical jazz vocalist <a href="http://www.carmenmcrae.com/">Carmen McRae</a> (whom we&#8217;ve <a href="http://www.last.fm/tag/wordpress-release-jazz">added to our Last.fm WP release station</a>). You can upgrade easily from your Dashboard by going to <strong>Tools</strong> &gt; <strong>Upgrade</strong>, or you can <a href="http://wordpress.org/download/">download from WordPress.org</a>. And of course, it wouldn&#8217;t be a major release without a short video summarizing some of the cool things about the new version:<br />
<embed src="http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.11" type="application/x-shockwave-flash" width="640" height="360" allowscriptaccess="always" allowfullscreen="true" flashvars="guid=NBZ853Xn&amp;width=640&amp;height=360" title="Introducing WordPress 2.9 Carmen"></embed></p>
<p>The coolest new stuff from a user point of view is:</p>
<ol>
<li><strong>Global undo/&#8221;trash&#8221; feature</strong>, which means that if you accidentally delete a post or comment you can bring it back from the grave (i.e., the Trash). This also eliminates those annoying &#8220;are you sure&#8221; messages we used to have on every delete.</li>
<li><strong>Built-in image editor</strong> allows you to crop, edit, rotate, flip, and scale your images to show them who&#8217;s boss. This is the first wave of our many planned media-handling improvements.</li>
<li><strong>Batch plugin update and compatibility checking,</strong> which means you can update 10 plugins at once, versus having to do multiple clicks for each one, and we&#8217;re using the new compatibility data from the plugins directory to give you a better idea of whether your plugins are compatible with new releases of WordPress. This should take the fear and hassle out of upgrading.</li>
<li><a href="http://codex.wordpress.org/Embeds"><strong>Easier video embeds</strong></a> that allow you to just paste a URL on its own line and have it magically turn it into the proper embed code, with Oembed support for YouTube, Daily Motion, Blip.tv, Flickr, Hulu, Viddler, Qik, Revision3, Scribd, Google Video, Photobucket, PollDaddy, and WordPress.tv (and more in the next release).</li>
</ol>
<p>2.9 provides the smoothest ride yet because of a number of improvements under the hood and more subtle improvements you&#8217;ll begin to appreciate once you&#8217;ve been around the block a few times. Here&#8217;s just a sampling:</p>
<ul>
<li>We now have <code>rel=canonical</code> support for better SEO.</li>
<li>There is automatic database optimization support, which you can enable in your <code>wp-config.php</code> file by adding <code>define('WP_ALLOW_REPAIR', true);</code>.</li>
<li>Themes can register &#8220;post thumbnails&#8221; which allow them to attach an image to the post, especially useful for magazine-style themes.</li>
<li>A new <code>commentmeta</code> table that allows arbitrary key/value pairs to be attached to comments, just like posts, so you can now expand greatly what you can do in the comment framework.</li>
<li>Custom post types have been upgraded with better API support so you can juggle more types than just post, page, and attachment. (More of this planned for 3.0.)</li>
<li>You can set custom theme directories, so a plugin can register a theme to be bundled with it or you can have multiple shared theme directories on your server.</li>
<li>We&#8217;ve upgraded TinyMCE WYSIWYG editing and Simplepie.</li>
<li>Sidebars can now have descriptions so it&#8217;s more obvious what and where they do what they do.</li>
<li>Specify category templates not just by ID, like before, but by slug, which will make it easier for theme developers to do custom things with categories &#8212; like post types!</li>
<li>Registration and profiles are now extensible to allow you to collect things more easily, like a user&#8217;s Twitter account or any other fields you can imagine.</li>
<li>The XML-RPC API has been extended to allow changing the user registration option. We fixed some Atom API attachment issues.</li>
<li>Create custom galleries with the new include and exclude attributes that allow you to pull attachments from any post, not just the current one.</li>
<li>When you&#8217;re editing files in the theme and plugin editors it remembers your location and takes you back to that line after you save. (Thank goodness!!!)</li>
<li>The Press This bookmarklet has been improved and is faster than ever; give it a try for on-the-fly blogging from wherever you are on the internet.</li>
<li>Custom taxonomies are now included in the WXR export file and imported correctly.</li>
<li>Better hooks and filters for excerpts, smilies, HTTP requests, user profiles, author links, taxonomies, SSL support, tag clouds, query_posts and WP_Query</li>
</ul>
<p>All of this and more is reflected in the <a href="http://core.trac.wordpress.org/query?status=closed&amp;milestone=2.9">over 500 tickets, bugs, and enhancements that WP developers in this release cycle</a>.</p>
<p>This release included code from over 140 contributors, here&#8217;s everyone we were able to identify: <a href="http://xavisys.com/">aaroncampbell (Aaron Campbell)</a>, <a href="http://sixohthree.com/">abackstrom (Adam Backstrom)</a>, <a href="http://www.aldenta.com/">aldenta (John Ford)</a>, <a href="http://alexking.org/">alexkingorg (Alex King)</a>, [amilanov], <a href="http://antony.lesuisse.org/">antonylesuisse (Antony Lesuisse)</a>, <a href="http://apeatling.wordpress.com/">apeatling (Andy Peatling)</a>, <a href="http://blog.apokalyptik.com/">apokalyptik (Demitrious Kelly)</a>, <a href="http://www.mailpress.org/">arena (André Renaut)</a>, <a href="http://digitalize.ca/">batmoo (Mohammad Jangda)</a>, <a href="http://bendunkle.com/">Ben Dunkle</a>, <a href="http://profiles.wordpress.org/benbe1987">BenBE1987</a>, <!--PROFILES.wp.org--> <a href="http://blog.bf-itservice.de/">Benjamin Flesch</a>, <a href="http://www.happyhumans.com/">bookchiq (Sarah Lewis)</a>, <a href="http://profiles.wordpress.org/brianwhite">brianwhite</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/c0nstruct">c0nstruct</a>, <!--PROFILES.wp.org--> <a href="http://www.caesarsgrunt.com/">caesarsgrunt (Caesar Schinas)</a>, <a href="http://kniffenwebdesign.com/">CalebKniffen (Caleb Kniffen)</a>, <a href="http://profiles.wordpress.org/chrisbliss18">chrisbliss18</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/chrisscott">chrisscott (Chris Scott)</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/christoph179">christoph179</a>, <!--PROFILES.wp.org--> <a href="http://coffee2code.com/">coffee2code (Scott Reilly)</a>, [cross country flight], <a href="http://www.curioso.org/">Curioso</a>, <a href="http://dave.pageportfolio.co.uk/">davecpage (Dave Page)</a>, <a href="http://dan-cole.com/">dcole07 (Dan Cole)</a>, <a href="http://dd32.id.au/">dd32 (Dion Hulse)</a>, <a href="http://op111.net/">demetris (Δημήτρης Κίκιζας)</a>, <a href="http://www.semiologic.com/">Denis-de-Bernardy</a>, <a href="http://profiles.wordpress.org/dj-wp">dj-wp</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/dwright">dwright</a>, <!--PROFILES.wp.org--> <a href="http://eddieringle.com/">eddieringle (Eddie Ringle)</a>, <a href="http://www.homelandstupidity.us/">error (Michael Hampton)</a>, <a href="http://profiles.wordpress.org/ewestp">ewestp</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/fabifott">fabifott</a>, <!--PROFILES.wp.org--> <a href="http://www.ilfilosofo.com/">filosofo (Austin Matzko)</a>, <a href="http://justintadlock.com/">greenshady (Justin Tadlock)</a>, <a href="http://gsnedders.com/">gsnedders/link92 (Geoffrey Sneddon)</a>, <a href="http://hailin.wordpress.com/">hailin (Hailin Wu)</a>, <a href="http://codex.wordpress.org/User:Hakre">hakre</a>, <!--CODEX.wp.org--> <a href="http://profiles.wordpress.org/hanilovesme">hanilovesme</a>, <!--PROFILES.wp.org--> <a href="http://ondskap.net/wp/">Harald Nesland</a>, <a href="http://profiles.wordpress.org/harrym">harrym</a>, <!--PROFILES.wp.org--> <a href="http://holizz.com/">holizz (Tom Adams)</a>, <a href="http://profiles.wordpress.org/ikonst">ikonst</a>, <!--PROFILES.wp.org--> <a href="http://jacobsantos.com/">jacobsantos (Jacob Santos)</a>, <a href="http://jane.wordpress.com/">janeforshort (Jane Wells)</a>, <a href="http://om4.com.au/">jamescollins (James Collins)</a>, <a href="http://bethesignal.org/">jdub (Jeff Waugh)</a>, <a href="http://www.modulaweb.fr/">jeff_ (Jean-François “Jeff” VIAL)</a>, <a href="http://simianuprising.com/">jeremyclarke (Jeremy Clarke)</a>, <a href="http://jeremy.visser.name/">JeremyVisser (Jeremy Visser)</a>, <a href="http://profiles.wordpress.org/jikamens">jikamens</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/jmulley">jmulley</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/joern_w">Joern_W</a>, <!--PROFILES.wp.org--> <a href="http://devel.kostdoktorn.se/">johanee (Johan Eenfeldt)</a>, <a href="http://lud.icro.us/">johnbillion (John Blackbourn)</a>, <a href="http://johnjamesjacoby.com/">johnjamesjacoby (John James Jacoby)</a>, <a href="http://profiles.wordpress.org/johnjosephbachir">johnjosephbachir (John Joseph Bachir)</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/jonathanrogers">JonathanRogers</a>, <!--PROFILES.wp.org--> <a href="http://yoast.com/">joostdevalk (Joost de Valk)</a>, <a href="http://rooibo.wordpress.com/">Jose Carlos Norte</a>, <a href="http://josephscott.org/">josephscott (Joseph Scott)</a>, <a href="http://tyco.ws/">junsuijin</a>, <a href="http://agapetry.net/">kevinB (Kevin Behrens)</a>, <a href="http://kometbomb.net/">kometbomb</a>, <a href="http://www.yuriko.net/">lilyfan (IKEDA Yuriko)</a>, [lostinlafayette], <a href="http://profiles.wordpress.org/madhyde">madhyde</a>, <!--PROFILES.wp.org--> <a href="http://subscribe2.wordpress.com/">MattyRob</a>, <a href="http://blogwaffe.com/">mdawaffe (Michael Adams)</a>, <a href="http://www.mittineague.com/">Mittineague</a>, <a href="http://blogyul.miqrogroove.com/">miqrogroove</a>, <a href="http://profiles.wordpress.org/morfiusx">morfiusx</a>, <!--PROFILES.wp.org--> <a href="http://www.misthaven.org.uk/blog/">mrmist (David McFarlane)</a>, <a href="http://nickmomrik.com/">mtdewvirus (Nick Momrik)</a>, <a href="http://urzenia.net/">mysz</a>, <a href="http://twitter.com/nacin">nacin (Andrew Nacin)</a>, <a href="http://thebookofjoe.com/">nanochrome</a>, <a href="http://blog.detlog.org/">nao (Naoko  McCracken)</a>, <a href="http://www.nathanrice.net/">nathanrice (Nathan Rice)</a>, <a href="http://nikolay.bg/">nbachiyski (Николай Бачийски)</a>, <a href="http://www.niallkennedy.com/">niallkennedy (Niall Kennedy)</a>, <a href="http://nickohrn.com/">nickohrn (Nick Ohrn)</a>, <a href="http://www.rpmurphy.com/">ninjaWR (Ryan Murphy)</a>, <a href="http://noel.io/">noel (Noël Jackson)</a>, <a href="http://ottodestruct.com/">Otto42 (Samuel Wood)</a>, <a href="https://redmine.kirdev.sch.bme.hu/">pairg</a>, <a href="https://peaceable-whale.pip.verisignlabs.com/">peaceablewhale (Franklin Tse)</a>, <a href="http://cnpstudio.com/">prettyboymp (Michael Pretty)</a>, <a href="http://www.prodevstudio.net">ProDevStudio</a>, <a href="http://www.bdihot.co.il/">ramiy</a>, <a href="http://www.red-sweater.com/blog/">redsweater (Daniel Jalkut)</a>, <a href="http://ruslany.net/">ruslany</a>, <a href="http://unlettered.org/">sambauers (Sam Bauers)</a>, <a href="http://scribu.net/">scribu</a>, <a href="http://profiles.wordpress.org/sewar">Sewar</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/simek">Simek</a>, <!--PROFILES.wp.org--> <a href="http://www.simonwheatley.co.uk/">simonwheatley (Simon Wheatley)</a>, <a href="http://www.poradnik-webmastera.com/">sirzooro (Daniel Frużyński)</a>, <a href="http://sivel.net/">sivel (Matt Martz)</a>, <a href="http://skeltoac.com/">skeltoac (Andy Skelton)</a>, <a href="http://smallvoid.com/about/">snakefoot</a>, <a href="http://stephanreiter.info/">stephanreiter (Stephan Reiter)</a>, <a href="http://striderweb.com/nerdaphernalia/">strider72 (Stephen Rider)</a>, <a href="http://profiles.wordpress.org/taco1991">taco1991</a>, <!--PROFILES.wp.org--> <a href="http://ideasilo.wordpress.com/">takayukister (Takayuki Miyoshi)</a>, <a href="http://tellyworth.wordpress.com/">tellyworth</a>, <a href="http://profiles.wordpress.org/tenpura">tenpura</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/usermrpapa">usermrpapa</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/utkarsh">utkarsh</a>, <!--PROFILES.wp.org--> <a href="http://www.viper007bond.com/">Viper007Bond</a>, <a href="http://blog.sjinks.org.ua/">vladimir_kolesnikov (Vladimir Kolesnikov)</a>, <a href="http://voxpelli.se/">VoxPelli (Pelle Wessman)</a>, [voyou1], <a href="http://emphaticallystatic.org/">wahgnube</a>, <a href="http://www.waltervos.com/">waltervos</a>, <a href="http://weston.ruter.net/">westonruter (Weston Ruter)</a>, <a href="http://willnorris.com/">wnorris (Will Norris)</a>, <a href="http://xentek.net/">xenlab (Eric Marden)</a>, <a href="http://blog.yoavfarhi.com/">yoavf (Yoav Farhi)</a>. Wowza!</p>
<p>2.9 has been an exciting development cycle, and I must say it has whetted our appetite for 3.0, which is coming next (probably this spring) and will include at the very least the merge of MU with the WordPress core, and a new default theme. We can&#8217;t wait to start working on it. But first, some Carmen McRae tunes and a beer. Join us! <img src='http://wordpress.org/development/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>(<em>After</em> you upgrade, of course!)</p>
<p>I hope everyone is having a wonderful holiday season.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2009/12/wordpress-2-9/feed/";}s:5:"slash";a:1:{s:8:"comments";s:2:"36";}s:7:"summary";s:360:"I want to make you mine, all the time&#8230; oh wait. Hello. I&#8217;m here on behalf of the entire WordPress development team and community to announce the immediate availability of WordPress version 2.9 &#8220;Carmen&#8221; named in honor of magical jazz vocalist Carmen McRae (whom we&#8217;ve added to our Last.fm WP release station). You can upgrade [...]";s:12:"atom_content";s:14105:"<p>I want to make you mine, all the time&#8230; oh wait. Hello. I&#8217;m here on behalf of the entire WordPress development team and community to announce the immediate availability of <a href="http://wordpress.org/download/">WordPress version 2.9 &#8220;Carmen&#8221;</a> named in honor of magical jazz vocalist <a href="http://www.carmenmcrae.com/">Carmen McRae</a> (whom we&#8217;ve <a href="http://www.last.fm/tag/wordpress-release-jazz">added to our Last.fm WP release station</a>). You can upgrade easily from your Dashboard by going to <strong>Tools</strong> &gt; <strong>Upgrade</strong>, or you can <a href="http://wordpress.org/download/">download from WordPress.org</a>. And of course, it wouldn&#8217;t be a major release without a short video summarizing some of the cool things about the new version:<br />
<embed src="http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.11" type="application/x-shockwave-flash" width="640" height="360" allowscriptaccess="always" allowfullscreen="true" flashvars="guid=NBZ853Xn&amp;width=640&amp;height=360" title="Introducing WordPress 2.9 Carmen"></embed></p>
<p>The coolest new stuff from a user point of view is:</p>
<ol>
<li><strong>Global undo/&#8221;trash&#8221; feature</strong>, which means that if you accidentally delete a post or comment you can bring it back from the grave (i.e., the Trash). This also eliminates those annoying &#8220;are you sure&#8221; messages we used to have on every delete.</li>
<li><strong>Built-in image editor</strong> allows you to crop, edit, rotate, flip, and scale your images to show them who&#8217;s boss. This is the first wave of our many planned media-handling improvements.</li>
<li><strong>Batch plugin update and compatibility checking,</strong> which means you can update 10 plugins at once, versus having to do multiple clicks for each one, and we&#8217;re using the new compatibility data from the plugins directory to give you a better idea of whether your plugins are compatible with new releases of WordPress. This should take the fear and hassle out of upgrading.</li>
<li><a href="http://codex.wordpress.org/Embeds"><strong>Easier video embeds</strong></a> that allow you to just paste a URL on its own line and have it magically turn it into the proper embed code, with Oembed support for YouTube, Daily Motion, Blip.tv, Flickr, Hulu, Viddler, Qik, Revision3, Scribd, Google Video, Photobucket, PollDaddy, and WordPress.tv (and more in the next release).</li>
</ol>
<p>2.9 provides the smoothest ride yet because of a number of improvements under the hood and more subtle improvements you&#8217;ll begin to appreciate once you&#8217;ve been around the block a few times. Here&#8217;s just a sampling:</p>
<ul>
<li>We now have <code>rel=canonical</code> support for better SEO.</li>
<li>There is automatic database optimization support, which you can enable in your <code>wp-config.php</code> file by adding <code>define('WP_ALLOW_REPAIR', true);</code>.</li>
<li>Themes can register &#8220;post thumbnails&#8221; which allow them to attach an image to the post, especially useful for magazine-style themes.</li>
<li>A new <code>commentmeta</code> table that allows arbitrary key/value pairs to be attached to comments, just like posts, so you can now expand greatly what you can do in the comment framework.</li>
<li>Custom post types have been upgraded with better API support so you can juggle more types than just post, page, and attachment. (More of this planned for 3.0.)</li>
<li>You can set custom theme directories, so a plugin can register a theme to be bundled with it or you can have multiple shared theme directories on your server.</li>
<li>We&#8217;ve upgraded TinyMCE WYSIWYG editing and Simplepie.</li>
<li>Sidebars can now have descriptions so it&#8217;s more obvious what and where they do what they do.</li>
<li>Specify category templates not just by ID, like before, but by slug, which will make it easier for theme developers to do custom things with categories &#8212; like post types!</li>
<li>Registration and profiles are now extensible to allow you to collect things more easily, like a user&#8217;s Twitter account or any other fields you can imagine.</li>
<li>The XML-RPC API has been extended to allow changing the user registration option. We fixed some Atom API attachment issues.</li>
<li>Create custom galleries with the new include and exclude attributes that allow you to pull attachments from any post, not just the current one.</li>
<li>When you&#8217;re editing files in the theme and plugin editors it remembers your location and takes you back to that line after you save. (Thank goodness!!!)</li>
<li>The Press This bookmarklet has been improved and is faster than ever; give it a try for on-the-fly blogging from wherever you are on the internet.</li>
<li>Custom taxonomies are now included in the WXR export file and imported correctly.</li>
<li>Better hooks and filters for excerpts, smilies, HTTP requests, user profiles, author links, taxonomies, SSL support, tag clouds, query_posts and WP_Query</li>
</ul>
<p>All of this and more is reflected in the <a href="http://core.trac.wordpress.org/query?status=closed&amp;milestone=2.9">over 500 tickets, bugs, and enhancements that WP developers in this release cycle</a>.</p>
<p>This release included code from over 140 contributors, here&#8217;s everyone we were able to identify: <a href="http://xavisys.com/">aaroncampbell (Aaron Campbell)</a>, <a href="http://sixohthree.com/">abackstrom (Adam Backstrom)</a>, <a href="http://www.aldenta.com/">aldenta (John Ford)</a>, <a href="http://alexking.org/">alexkingorg (Alex King)</a>, [amilanov], <a href="http://antony.lesuisse.org/">antonylesuisse (Antony Lesuisse)</a>, <a href="http://apeatling.wordpress.com/">apeatling (Andy Peatling)</a>, <a href="http://blog.apokalyptik.com/">apokalyptik (Demitrious Kelly)</a>, <a href="http://www.mailpress.org/">arena (André Renaut)</a>, <a href="http://digitalize.ca/">batmoo (Mohammad Jangda)</a>, <a href="http://bendunkle.com/">Ben Dunkle</a>, <a href="http://profiles.wordpress.org/benbe1987">BenBE1987</a>, <!--PROFILES.wp.org--> <a href="http://blog.bf-itservice.de/">Benjamin Flesch</a>, <a href="http://www.happyhumans.com/">bookchiq (Sarah Lewis)</a>, <a href="http://profiles.wordpress.org/brianwhite">brianwhite</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/c0nstruct">c0nstruct</a>, <!--PROFILES.wp.org--> <a href="http://www.caesarsgrunt.com/">caesarsgrunt (Caesar Schinas)</a>, <a href="http://kniffenwebdesign.com/">CalebKniffen (Caleb Kniffen)</a>, <a href="http://profiles.wordpress.org/chrisbliss18">chrisbliss18</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/chrisscott">chrisscott (Chris Scott)</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/christoph179">christoph179</a>, <!--PROFILES.wp.org--> <a href="http://coffee2code.com/">coffee2code (Scott Reilly)</a>, [cross country flight], <a href="http://www.curioso.org/">Curioso</a>, <a href="http://dave.pageportfolio.co.uk/">davecpage (Dave Page)</a>, <a href="http://dan-cole.com/">dcole07 (Dan Cole)</a>, <a href="http://dd32.id.au/">dd32 (Dion Hulse)</a>, <a href="http://op111.net/">demetris (Δημήτρης Κίκιζας)</a>, <a href="http://www.semiologic.com/">Denis-de-Bernardy</a>, <a href="http://profiles.wordpress.org/dj-wp">dj-wp</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/dwright">dwright</a>, <!--PROFILES.wp.org--> <a href="http://eddieringle.com/">eddieringle (Eddie Ringle)</a>, <a href="http://www.homelandstupidity.us/">error (Michael Hampton)</a>, <a href="http://profiles.wordpress.org/ewestp">ewestp</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/fabifott">fabifott</a>, <!--PROFILES.wp.org--> <a href="http://www.ilfilosofo.com/">filosofo (Austin Matzko)</a>, <a href="http://justintadlock.com/">greenshady (Justin Tadlock)</a>, <a href="http://gsnedders.com/">gsnedders/link92 (Geoffrey Sneddon)</a>, <a href="http://hailin.wordpress.com/">hailin (Hailin Wu)</a>, <a href="http://codex.wordpress.org/User:Hakre">hakre</a>, <!--CODEX.wp.org--> <a href="http://profiles.wordpress.org/hanilovesme">hanilovesme</a>, <!--PROFILES.wp.org--> <a href="http://ondskap.net/wp/">Harald Nesland</a>, <a href="http://profiles.wordpress.org/harrym">harrym</a>, <!--PROFILES.wp.org--> <a href="http://holizz.com/">holizz (Tom Adams)</a>, <a href="http://profiles.wordpress.org/ikonst">ikonst</a>, <!--PROFILES.wp.org--> <a href="http://jacobsantos.com/">jacobsantos (Jacob Santos)</a>, <a href="http://jane.wordpress.com/">janeforshort (Jane Wells)</a>, <a href="http://om4.com.au/">jamescollins (James Collins)</a>, <a href="http://bethesignal.org/">jdub (Jeff Waugh)</a>, <a href="http://www.modulaweb.fr/">jeff_ (Jean-François “Jeff” VIAL)</a>, <a href="http://simianuprising.com/">jeremyclarke (Jeremy Clarke)</a>, <a href="http://jeremy.visser.name/">JeremyVisser (Jeremy Visser)</a>, <a href="http://profiles.wordpress.org/jikamens">jikamens</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/jmulley">jmulley</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/joern_w">Joern_W</a>, <!--PROFILES.wp.org--> <a href="http://devel.kostdoktorn.se/">johanee (Johan Eenfeldt)</a>, <a href="http://lud.icro.us/">johnbillion (John Blackbourn)</a>, <a href="http://johnjamesjacoby.com/">johnjamesjacoby (John James Jacoby)</a>, <a href="http://profiles.wordpress.org/johnjosephbachir">johnjosephbachir (John Joseph Bachir)</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/jonathanrogers">JonathanRogers</a>, <!--PROFILES.wp.org--> <a href="http://yoast.com/">joostdevalk (Joost de Valk)</a>, <a href="http://rooibo.wordpress.com/">Jose Carlos Norte</a>, <a href="http://josephscott.org/">josephscott (Joseph Scott)</a>, <a href="http://tyco.ws/">junsuijin</a>, <a href="http://agapetry.net/">kevinB (Kevin Behrens)</a>, <a href="http://kometbomb.net/">kometbomb</a>, <a href="http://www.yuriko.net/">lilyfan (IKEDA Yuriko)</a>, [lostinlafayette], <a href="http://profiles.wordpress.org/madhyde">madhyde</a>, <!--PROFILES.wp.org--> <a href="http://subscribe2.wordpress.com/">MattyRob</a>, <a href="http://blogwaffe.com/">mdawaffe (Michael Adams)</a>, <a href="http://www.mittineague.com/">Mittineague</a>, <a href="http://blogyul.miqrogroove.com/">miqrogroove</a>, <a href="http://profiles.wordpress.org/morfiusx">morfiusx</a>, <!--PROFILES.wp.org--> <a href="http://www.misthaven.org.uk/blog/">mrmist (David McFarlane)</a>, <a href="http://nickmomrik.com/">mtdewvirus (Nick Momrik)</a>, <a href="http://urzenia.net/">mysz</a>, <a href="http://twitter.com/nacin">nacin (Andrew Nacin)</a>, <a href="http://thebookofjoe.com/">nanochrome</a>, <a href="http://blog.detlog.org/">nao (Naoko  McCracken)</a>, <a href="http://www.nathanrice.net/">nathanrice (Nathan Rice)</a>, <a href="http://nikolay.bg/">nbachiyski (Николай Бачийски)</a>, <a href="http://www.niallkennedy.com/">niallkennedy (Niall Kennedy)</a>, <a href="http://nickohrn.com/">nickohrn (Nick Ohrn)</a>, <a href="http://www.rpmurphy.com/">ninjaWR (Ryan Murphy)</a>, <a href="http://noel.io/">noel (Noël Jackson)</a>, <a href="http://ottodestruct.com/">Otto42 (Samuel Wood)</a>, <a href="https://redmine.kirdev.sch.bme.hu/">pairg</a>, <a href="https://peaceable-whale.pip.verisignlabs.com/">peaceablewhale (Franklin Tse)</a>, <a href="http://cnpstudio.com/">prettyboymp (Michael Pretty)</a>, <a href="http://www.prodevstudio.net">ProDevStudio</a>, <a href="http://www.bdihot.co.il/">ramiy</a>, <a href="http://www.red-sweater.com/blog/">redsweater (Daniel Jalkut)</a>, <a href="http://ruslany.net/">ruslany</a>, <a href="http://unlettered.org/">sambauers (Sam Bauers)</a>, <a href="http://scribu.net/">scribu</a>, <a href="http://profiles.wordpress.org/sewar">Sewar</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/simek">Simek</a>, <!--PROFILES.wp.org--> <a href="http://www.simonwheatley.co.uk/">simonwheatley (Simon Wheatley)</a>, <a href="http://www.poradnik-webmastera.com/">sirzooro (Daniel Frużyński)</a>, <a href="http://sivel.net/">sivel (Matt Martz)</a>, <a href="http://skeltoac.com/">skeltoac (Andy Skelton)</a>, <a href="http://smallvoid.com/about/">snakefoot</a>, <a href="http://stephanreiter.info/">stephanreiter (Stephan Reiter)</a>, <a href="http://striderweb.com/nerdaphernalia/">strider72 (Stephen Rider)</a>, <a href="http://profiles.wordpress.org/taco1991">taco1991</a>, <!--PROFILES.wp.org--> <a href="http://ideasilo.wordpress.com/">takayukister (Takayuki Miyoshi)</a>, <a href="http://tellyworth.wordpress.com/">tellyworth</a>, <a href="http://profiles.wordpress.org/tenpura">tenpura</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/usermrpapa">usermrpapa</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/utkarsh">utkarsh</a>, <!--PROFILES.wp.org--> <a href="http://www.viper007bond.com/">Viper007Bond</a>, <a href="http://blog.sjinks.org.ua/">vladimir_kolesnikov (Vladimir Kolesnikov)</a>, <a href="http://voxpelli.se/">VoxPelli (Pelle Wessman)</a>, [voyou1], <a href="http://emphaticallystatic.org/">wahgnube</a>, <a href="http://www.waltervos.com/">waltervos</a>, <a href="http://weston.ruter.net/">westonruter (Weston Ruter)</a>, <a href="http://willnorris.com/">wnorris (Will Norris)</a>, <a href="http://xentek.net/">xenlab (Eric Marden)</a>, <a href="http://blog.yoavfarhi.com/">yoavf (Yoav Farhi)</a>. Wowza!</p>
<p>2.9 has been an exciting development cycle, and I must say it has whetted our appetite for 3.0, which is coming next (probably this spring) and will include at the very least the merge of MU with the WordPress core, and a new default theme. We can&#8217;t wait to start working on it. But first, some Carmen McRae tunes and a beer. Join us! <img src='http://wordpress.org/development/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>(<em>After</em> you upgrade, of course!)</p>
<p>I hope everyone is having a wonderful holiday season.</p>
";}i:8;a:13:{s:5:"title";s:21:"2010: A Theme Odyssey";s:4:"link";s:62:"http://wordpress.org/development/2009/12/2010-a-theme-odyssey/";s:8:"comments";s:71:"http://wordpress.org/development/2009/12/2010-a-theme-odyssey/#comments";s:7:"pubdate";s:31:"Fri, 18 Dec 2009 18:36:43 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:34:"Development2010defaultkubricktheme";s:4:"guid";s:40:"http://wordpress.org/development/?p=1065";s:11:"description";s:327:"After the video from the core team meetup was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt&#8217;s announcement that there would be a new default theme in 2010, so I thought I&#8217;d start with that as the first of the meetup summaries.
When Kubrick was bundled [...]";s:7:"content";a:1:{s:7:"encoded";s:2819:"<p>After the <a href="http://wordpress.org/development/2009/12/core-team-meetup-results/">video from the core team meetup</a> was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt&#8217;s announcement that there would be a new default theme in 2010, so I thought I&#8217;d start with that as the first of the meetup summaries.</p>
<p>When Kubrick was bundled with core back in 2005, it was a cutting edge theme. Custom header, rounded corners, clean design&#8230; if you were using WordPress back then, let&#8217;s face it, you were impressed. Time moves on, though, fashions change, new styles become old standards, and what was once cutting edge suddenly seems old-fashioned and out of date.</p>
<p>So, a new bundled theme in 2010? We think it&#8217;s a good idea. Something nice and light that can serve as a good example theme, include newer theme-based features, and look nice (and current) on a public site. We&#8217;d like to introduce a new default theme with version 3.0, which is anticipated to come out in mid-2010 (hence the name), and think it would be good for it to blend well aesthetically with WordPress itself.</p>
<p>I&#8217;d been advocating moving toward <a href="http://elastictheme.org/">Elastic</a>, the theme framework/WYSIWYG theme editor that was one of our Google Summer of Code student projects, but after some discussion I agreed with the guys that while Elastic is awesome and should be promoted as a community development project, it&#8217;s heavier than a default theme needs to be. The default theme doesn&#8217;t need to be a full-featured framework, it just needs to work well, look awesome, have good code and be a good starting point for beginning themers. We were thinking of a fairly minimalist design that would make it easy to customize.</p>
<p>As for the code, there&#8217;s a question of if it will really be a new theme, or if it will be a re-styled and updated version of Kubrick.  We don&#8217;t know the final answer to that yet, because the ultimate decision will be made with the community&#8217;s input, but we believe all new markup is the way to go. What do you think? Without venturing into theme framework territory, are there features you think a new default theme should have? Some people have been <a href="http://core.trac.wordpress.org/ticket/9015">talking about it on Trac</a> over the past year, if you wonder what&#8217;s been tossed around so far. I thought about posting a poll here (you know how I love posting polls to gauge opinion), but in this case I think a discussion thread might be better, so that each vote can explain the reason behind it. So, have an opinion on what a new default theme should include? <a href="http://wordpress.org/support/topic/342819">Weigh in at the forums</a>.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:67:"http://wordpress.org/development/2009/12/2010-a-theme-odyssey/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:327:"After the video from the core team meetup was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt&#8217;s announcement that there would be a new default theme in 2010, so I thought I&#8217;d start with that as the first of the meetup summaries.
When Kubrick was bundled [...]";s:12:"atom_content";s:2819:"<p>After the <a href="http://wordpress.org/development/2009/12/core-team-meetup-results/">video from the core team meetup</a> was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt&#8217;s announcement that there would be a new default theme in 2010, so I thought I&#8217;d start with that as the first of the meetup summaries.</p>
<p>When Kubrick was bundled with core back in 2005, it was a cutting edge theme. Custom header, rounded corners, clean design&#8230; if you were using WordPress back then, let&#8217;s face it, you were impressed. Time moves on, though, fashions change, new styles become old standards, and what was once cutting edge suddenly seems old-fashioned and out of date.</p>
<p>So, a new bundled theme in 2010? We think it&#8217;s a good idea. Something nice and light that can serve as a good example theme, include newer theme-based features, and look nice (and current) on a public site. We&#8217;d like to introduce a new default theme with version 3.0, which is anticipated to come out in mid-2010 (hence the name), and think it would be good for it to blend well aesthetically with WordPress itself.</p>
<p>I&#8217;d been advocating moving toward <a href="http://elastictheme.org/">Elastic</a>, the theme framework/WYSIWYG theme editor that was one of our Google Summer of Code student projects, but after some discussion I agreed with the guys that while Elastic is awesome and should be promoted as a community development project, it&#8217;s heavier than a default theme needs to be. The default theme doesn&#8217;t need to be a full-featured framework, it just needs to work well, look awesome, have good code and be a good starting point for beginning themers. We were thinking of a fairly minimalist design that would make it easy to customize.</p>
<p>As for the code, there&#8217;s a question of if it will really be a new theme, or if it will be a re-styled and updated version of Kubrick.  We don&#8217;t know the final answer to that yet, because the ultimate decision will be made with the community&#8217;s input, but we believe all new markup is the way to go. What do you think? Without venturing into theme framework territory, are there features you think a new default theme should have? Some people have been <a href="http://core.trac.wordpress.org/ticket/9015">talking about it on Trac</a> over the past year, if you wonder what&#8217;s been tossed around so far. I thought about posting a poll here (you know how I love posting polls to gauge opinion), but in this case I think a discussion thread might be better, so that each vote can explain the reason behind it. So, have an opinion on what a new default theme should include? <a href="http://wordpress.org/support/topic/342819">Weigh in at the forums</a>.</p>
";}i:9;a:13:{s:5:"title";s:23:"2.9 Release Candidate 1";s:4:"link";s:49:"http://wordpress.org/development/2009/12/2-9-rc1/";s:8:"comments";s:58:"http://wordpress.org/development/2009/12/2-9-rc1/#comments";s:7:"pubdate";s:31:"Wed, 16 Dec 2009 18:33:39 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:11:"Development";s:4:"guid";s:40:"http://wordpress.org/development/?p=1057";s:11:"description";s:335:"We&#8217;re at that exciting point in WordPress development where the dev team feels like version 2.9 is complete and ready for the world.
If you&#8217;ve been waiting for your moment to pitch in, it&#8217;s now. First we need tech savvy testers to upgrade their blogs and kick the tires, make sure everything is rolling like you [...]";s:7:"content";a:1:{s:7:"encoded";s:1702:"<p>We&#8217;re at that exciting point in WordPress development where the dev team feels like version 2.9 is complete and ready for the world.</p>
<p>If you&#8217;ve been waiting for your moment to pitch in, it&#8217;s now. First we need tech savvy testers to upgrade their blogs and kick the tires, make sure everything is rolling like you expect it to. <a href="http://codex.wordpress.org/Version_2.9">Here&#8217;s a list of all the fun and geeky new stuff in 2.9 to try out</a>. Second, and more importantly, we need everyone to test out their plugin compatibility.</p>
<p>If you&#8217;re a user of plugins, there&#8217;s a groovy new compatibility feature on the plugin directory where you can vote on whether a plugin is compatible with a version or not and it&#8217;ll get registered in the new plugin compatibility checker. This is as a replacement to the old wiki-based lists we&#8217;d do before. To see it in action <a href="http://wordpress.org/extend/plugins/akismet/">check out this Akismet plugin page</a>, as you can see 14 people have already registered that it&#8217;s compatible with 2.9.</p>
<p>If you&#8217;re a plugin author, of course you should update your &#8220;Tested up to:&#8221; in the <code>readme.txt</code> for your plugin.</p>
<p>If all goes according to plan, WordPress 2.9 will be out before the end of the week. <a href="http://wordpress.org/wordpress-2.9-RC1.zip">You can download the release candidate here</a>.</p>
<p>For more details on the changes since Beta please review the <a href="https://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=12416&amp;stop_rev=12315&amp;limit=150">revision log on Trac</a>, and happy testing!</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:54:"http://wordpress.org/development/2009/12/2-9-rc1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:335:"We&#8217;re at that exciting point in WordPress development where the dev team feels like version 2.9 is complete and ready for the world.
If you&#8217;ve been waiting for your moment to pitch in, it&#8217;s now. First we need tech savvy testers to upgrade their blogs and kick the tires, make sure everything is rolling like you [...]";s:12:"atom_content";s:1702:"<p>We&#8217;re at that exciting point in WordPress development where the dev team feels like version 2.9 is complete and ready for the world.</p>
<p>If you&#8217;ve been waiting for your moment to pitch in, it&#8217;s now. First we need tech savvy testers to upgrade their blogs and kick the tires, make sure everything is rolling like you expect it to. <a href="http://codex.wordpress.org/Version_2.9">Here&#8217;s a list of all the fun and geeky new stuff in 2.9 to try out</a>. Second, and more importantly, we need everyone to test out their plugin compatibility.</p>
<p>If you&#8217;re a user of plugins, there&#8217;s a groovy new compatibility feature on the plugin directory where you can vote on whether a plugin is compatible with a version or not and it&#8217;ll get registered in the new plugin compatibility checker. This is as a replacement to the old wiki-based lists we&#8217;d do before. To see it in action <a href="http://wordpress.org/extend/plugins/akismet/">check out this Akismet plugin page</a>, as you can see 14 people have already registered that it&#8217;s compatible with 2.9.</p>
<p>If you&#8217;re a plugin author, of course you should update your &#8220;Tested up to:&#8221; in the <code>readme.txt</code> for your plugin.</p>
<p>If all goes according to plan, WordPress 2.9 will be out before the end of the week. <a href="http://wordpress.org/wordpress-2.9-RC1.zip">You can download the release candidate here</a>.</p>
<p>For more details on the changes since Beta please review the <a href="https://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=12416&amp;stop_rev=12315&amp;limit=150">revision log on Trac</a>, and happy testing!</p>
";}}s:7:"channel";a:8:{s:5:"title";s:26:"WordPress Development Blog";s:4:"link";s:32:"http://wordpress.org/development";s:11:"description";s:33:"WordPress development and updates";s:13:"lastbuilddate";s:31:"Fri, 22 Jan 2010 05:38:09 +0000";s:9:"generator";s:29:"http://wordpress.org/?v=2.9.1";s:8:"language";s:2:"en";s:2:"sy";a:2:{s:12:"updateperiod";s:6:"hourly";s:15:"updatefrequency";s:1:"1";}s:7:"tagline";s:33:"WordPress development and updates";}s:9:"textinput";a:0:{}s:5:"image";a:0:{}s:9:"feed_type";s:3:"RSS";s:12:"feed_version";s:3:"2.0";s:5:"stack";a:0:{}s:9:"inchannel";b:0;s:6:"initem";b:0;s:9:"incontent";b:0;s:11:"intextinput";b:0;s:7:"inimage";b:0;s:13:"current_field";s:0:"";s:17:"current_namespace";b:0;s:19:"_CONTENT_CONSTRUCTS";a:6:{i:0;s:7:"content";i:1;s:7:"summary";i:2;s:4:"info";i:3;s:5:"title";i:4;s:7:"tagline";i:5;s:9:"copyright";}}