WordPress is a user-driven project, and all developments and enhancements depend on users like you! Please consider contributing to the project and the WordPress Community in one or more of the ways outlined below. Contributions from users like you keep the project vibrant, alive, and on the path of progress.

Whether you’re a budding developer, a pixel-perfect designer, or just like helping out, we’re always looking for people to help make WordPress even better. Below is an overview of ways to get involved and help out. If you want to dive right in, visit https://make.wordpress.org/.

Documentation

All of the WordPress user and developer documentation has been produced by users like you and me! The many different ways in which you can volunteer your time and effort to improve the quality and scope of documentation are outlined in Documentation Contributor Handbook.

The slack channel #docs is the forum for discussing all issues related to documentation.

Translation

Translating WordPress describes the process of translating the WordPress software, so that people can use WordPress for blogs in languages other than English. This article tells you how to find and join the teams that are translating WordPress.

The slack channel #polyglots is for questions, suggestions and discussions related to translating WordPress; please feel free to join in.

To get involved with the Translation team, please review https://make.wordpress.org/polyglots/.

WordPress Support Forum

Another valuable contribution you can make is donating some of your time to help other users of WordPress. All WordPress related support at the WordPress Support Forum is provided free of cost, and the involvement of users is essential to maintain this.

If you’d like to help, read visit https://make.wordpress.org/support/ for more information.

WordPress Chat on Slack

Slack has replaced IRC as a way to organize and get work done on WordPress. The community is vibrant, responsive, and very active. Please join us on our Slack channel and start getting involved today.

There is a weekly meetup of core developers in #core on Slack. Agendas, minutes, and discussion between meetups all take place on the WordPress Development Blog.

While the IRC Live chat is still active, our Slack Channel is where we are getting work done. Please join us on http://chat.wordpress.org

WordPress Development

You can help with the development of the WordPress software, whether or not you are a software developer.

Development Planning

One way to participate in WordPress development is to suggest features and participate in the development planning process. Even if you aren’t a developer, you can help build consensus and formalize proposals, boiling down long email threads and IRC logs to their essence, so that developers can quickly ascertain what the community is hoping to achieve with a particular feature.

Testing WordPress

Another valuable contribution a non-developer (or developer) can make to WordPress development is to test WordPress. Before every stable release of WordPress, pre-release versions are made to enable testing. You can download the pre-releases and test them, so that the WordPress developers can fix problems before the new version is made available to the public. If you would like to get involved in this effort, join the wp-testers mailing list, where new releases are announced and discussed.

If you want to be on the bleeding edge of development, even before pre-release versions are put together, you can also check out the latest software from the WordPress Subversion (SVN) repository, as outlined in Using Subversion. Or, you can get the “nightly build” (which is created from the Subversion repository, and available as a zip file) at https://wordpress.org/nightly-builds/wordpress-latest.zip — almost as up-to-date as the instantaneous Subversion repository.

If you find bugs while testing pre-release or already-released versions of WordPress, see the section just below.

Reporting Bugs

Another way you can contribute to WordPress development is by reporting any problems you find with the WordPress software. The process of reporting bugs is described in Reporting Bugs — please start by reading that article. Once you have understood the bug reporting process, you can search the WordPress Trac database to see if your issue has already been reported, and if not, file a new report. Your help with reporting bugs will be highly appreciated.

Fixing Bugs and Other Programming

If you are a software developer, you can also help the development of WordPress by fixing problems that have been reported by you or another person in the WordPress Trac database. This process is also known as “patching”, and is described in Reporting Bugs. That article also has some suggestions on how to find bugs to fix.

You can also subscribe to the wp-hackers mailing list to participate in discussions regarding WordPress development. All contributions, ideas and suggestions are welcome at the mailing list. Sometimes, requests are also made on the list asking for the help of volunteers to assist in the improvement and development of specific functionality.

If you are not familiar with the patching process or how to use Subversion, we recommend OpenHatch Training Missions as an easy learning tool.

Occasionally there are also bug scrubs in the #core Slack channel. They are usually announced ahead of time on the make/core blog, and more details about what a bug scrub involves is available in the core team handbook.

You may also be interested to read this page on How does code make it into WordPress. It details how bug fixes, code and new features are included into the next releases of WordPress.

Show You Care

If you enjoy WordPress or find it to be useful, put a link to WordPress on your site. You can do this with a text link, or use one of the many WordPress logos on your site with a link to http://wordpress.org. Show you care.

Donating Money

The WordPress Community exists because everyone takes part in some way, by giving their time, energy, and sometimes even money, because they believe in the valuable services WordPress provides. We invite you to join the community in whatever way you feel is appropriate, and donating money to WordPress Theme and Plugin authors and developers who give so freely of their creativity and expertise by offering their services for free to all WordPress users is a good place to start.

If you use a WordPress Theme or Plugin and your WordPress blog depends upon it, contact the author and find out how you can give back and support their continued efforts. It takes a lot of time and energy to create and then support Themes and Plugins, keeping them updated as WordPress changes and bugs are found. Many take donations or appreciate it when you blog about their Plugin or Theme. Others offer their Plugins and Themes as experiential portfolios– you play with it, you like it, you hire them. Most clearly indicate how they appreciate compensation for their hard work – give back to WordPress by giving back to them.

The more the WordPress Community supports the programmers, developers, testers, and challengers, the stronger and better WordPress becomes. Sometimes that means donating money, sometimes it means saying thank you.

Just remember, every contribution counts, no matter what it looks like. It takes every one of us to make WordPress better.

There are also various post launch versions with improvements for security, bug fixes and stability. Please review the full WordPress Release Archive for details or check out the version announcements!

2023 – Announcement: 6.2, 6.3, 6.4

Version 6.4 (Shirley): (>600 contributors) Say hello to WordPress 6.4 “Shirley,” named after the iconic jazz artist Shirley Horn. Her distinctive voice and extraordinary connection to the piano established her as one of the leading jazz musicians of her generation. Horn’s journey from the Washington D.C. jazz scene to the international stage is a testament to her dedication and perseverance. Her influence reached far beyond the confines of traditional jazz, breaking boundaries and inspiring audiences worldwide.

Version 6.3 (Lionel): (536 contributors) Say hello to WordPress 6.3 “Lionel,” named after Lionel Hampton, the celebrated American jazz artist. A prolific jazz vibraphonist, pianist, and percussionist, Hampton gained notoriety working in harmony with greats from Charles Mingus to Quincy Jones and as bandleader of the eponymous Lionel Hampton Orchestra. His artistry and charitable work have been recognized with a Grammy, a star on the Hollywood Walk of Fame, and the National Medal of Arts.

Version 6.2 (Dolphy): (600 contributors) Say hello to WordPress 6.2 “Dolphy,” named for the woodwind jazz wiz, the multi-instrumentalist—Eric Allan Dolphy Jr. Dolphy is acclaimed for having brought the bass clarinet to prominence in the jazz scene, creating a place for the flute and extending the lexicon of the alto saxophone. In a career that spanned continents, his artistry was at the forefront of pushing improvisational boundaries, ensemble work, and partnerships with well-respected artists like Charles Mingus and John Coltrane.

2022 – Announcement(s): 5.9, 6.0, 6.1

Version 6.1 (Misha): (800 contributors) Say hello to “Misha,” the WordPress 6.1 release, inspired by Mikhail “Misha” Alperin acclaimed jazz ensemblist and composer. Site owners and administrators should upgrade today to take full advantage of the many stability, performance, and usability enhancements. Furthermore, WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.

Version 6.0 (Arturo): (500 contributors) Say hello to “Arturo” and WordPress 6.0, inspired by Grammy-winning jazz musician, Arturo O’Farrill. With nearly 1,000 enhancements and bug fixes, the second major release of 2022 is here. Site owners and administrators should upgrade to take full advantage of the many stability, performance, and usability enhancements today. WordPress content creators will enjoy a suite of new features geared toward improving the writing and designing experiences.

Version 5.9 (Joséphine): (624 contributors) Full site editing arrives and puts you in control of your whole site, right in the WordPress Admin. A new default block theme, Twenty Twenty-Two, shows off the wide array of visual choices all from the Site Editor. The new Navigation block provides an always-on responsive menu, one that adapts to your user’s screen size. Better block controls, the new Pattern Directory, a revamped List View, and a better Gallery block round out the new tweaks to the publishing flow to help you say more, faster.

2021 – Announcements: 5.7, 5.8

Version 5.8 (Tatum): (530 contributors) The power of blocks has come to both the Block Widgets Editor and the Customizer. The Query Loop Block makes it possible to display posts based on specified parameters. You can also use the familiar block editor to edit templates that hold your content. Worth noting that support for Internet Explorer 11 has been dropped as of this release. WordPress 5.8 also adds support for WebP images.

Version 5.7 (Esperanza): (481 contributors) With this new version, WordPress brings you fresh colors. The editor helps you work in a few places you couldn’t before without getting into code or hiring a pro. The controls you use most are right where you need them. Layout changes that should be simple, are even simpler to make.

2020 – Announcements: 5.4, 5.5, 5.6

Version 5.6 (Simone): (605 contributors) brings you countless ways to set your ideas free and bring them to life. With a brand-new default theme as your canvas, it supports an ever-growing collection of blocks as your brushes. Paint with words. Pictures. Sound. Or rich embedded media.

Version 5.5 (Eckstine): (809 contributors) added speed, search and security improvements to WordPress. The block editor also received a lot of improvements with blocks patterns, inline image editing, and a brand new block directory. In addition to that, this release also made big changes for developers; in the REST API, to the dashicons, environment variables, etc.

Version 5.4 (Adderley): (595 contributors) added more ways to make posts and pages come alive with your best images, to bring your visitors in, and keep them engaged, with the richness of embedded media from the web’s top services. This version also added more speed everywhere within the administration dashboard and websites frontend.

2019 – Announcements: 5.1, 5.2, 5.3

Version 5.3 (Kirk): (711 contributors) expanded and refined the block editor introduced in WordPress 5.0 with new blocks, more intuitive interactions, and improved accessibility. New features in the editor increase design freedoms, provide additional layout options and style variations to allow designers complete control over the look of a site. This release also introduces the Twenty Twenty theme giving the user more design flexibility and integration with the block editor.

Version 5.2 (Jaco): (389 contributors) added more robust tools for identifying and fixing configuration issues and fatal errors. For both websites developers and people managing their sites by themselves, these tools can help get the right information about a website when needed.

Version 5.1 (Betty): (552 contributors) focused on polish, in particular by improving performance of the editor. In addition, this release paves the way for a better, faster, and more secure WordPress with some essential tools for site administrators and developers.

2018 – Announcement: 5.0

Version 5.0 (Bebo): (432 Contributors) introduced a new block based editor with a showcase theme (Twenty Nineteen). Support for the classic editor was maintained and the community translated the release to support a total of 37 languages.

2017 – Announcements: 4.8, 4.9

Version 4.9 (Tipton) (443 Contributors) focused on user experience and introduced the ability to save design drafts for review and alteration prior to publishing. Design locking rolled out, protecting two multiple designers to override changes in progress. This was also the introduction point of code syntax checking and error reporting within the Admin experience. An official callout for contributors and testers went out for the Gutenberg project.

Version 4.8 (Evans) (346 Contributors) brought an array of new widgets (image, video, audio and rich text). Adding links improved greatly setting boundaries around groupings of text to avoid mismatching. WordPress event streams became visible in the Admin Dashboard. Developer enhancements were introduced for added accessibility, API introduction to make the editor more portable to different areas via plugins.

2016 – Announcements: 4.5, 4.6, 4.7

Version 4.7 (Vaughan) (482 Contributors) arrived along side a new theme with modern elements (including starter content) with video header support. New Customizer features allow editing CSS with live previewing. REST API endpoints allow for machine-readable external access for enhanced third party interaction. Page template functionality was opened up to all post types. Bulk actions additionally were branched out with custom option support. The Customizer continued extension to support auto saving of drafts. This was an exciting release for WordPress as the number of contributors significantly increased with this release.

Version 4.6 (Pepper) (272 Contributors) brought significant speed changes to Multisite with cached and comprehensive site queries to improve the network admin experience. Theme addition, activation and plugin updates were adapted to a one screen process. Local draft saving to browser was introduced. Native fonts were also made available to be used from the operating system for speed enhancement.

Version 4.5 (Coleman) (298 Contributors) added inline links, added formatting shortcuts and responsive previews in Customizer to preview on mobile, tablet or desktop. Additionally, support was added for Custom Logos, smart image resizing for speed improvement and script loading improvements for dependent scripts from the header and footer.

2015 – Announcements: 4.2, 4.3, 4.4

Winner of CMS Critic Award’s “Best CMS for Personal Websites.”

Version 4.4 (Clifford) (471 Contributors) added responsive images, embeddable posts, and a new default theme, “Twenty Sixteen.” oEmbed support was added for WordPress posts with rich previews and display as well as five new providers (Cloudup, Reddit Comments, ReverbNation, Speaker Deck, and VideoPress). Developer improvements included integration of the REST API structure, query improvements for comments, Term Metadata and two new Objects (Term and Network) for more predictable added interaction capability within code.

Version 4.3 (Billie) (246 Contributors) added built-in site icons support and introduced formatting shortcuts in the visual editor. Live Menu previews became available from the Customizer. Password processes were improved for security as well as List Views in the Admin panel.

Version 4.2 (Powell) (283 Contributors) added emoji support, add extended character support and switched database encoding from utf8 to utf8mb4. Plugin updates became dynamic from one page without reloading. Two new oEmbed providers were added (Tumblr, Kickstarter). Theme switching became available through the Customizer. This version also included developer query improvements.

2014 – Announcements: 3.9, 4.0, 4.1

Version 4.1 (Dinah) (283 Contributors) introduced a refreshed Distraction Free Writing mode, language installation from the Settings screen (to switch between 40 different languages with support from Google’s Noto font family), and a beautiful new default theme, “Twenty Fifteen.” Developer improvements included addition of advanced metadata query conditional logic.

Version 4.0 (Benny) (275 Contributors) introduced a grid view for the media library and for installing plugins. Previews for embedded content such as Twitter and YouTube became available from within the editor while preparing content. Editor writing improvements included expanding the editor with content for an easier experience. The Plugin section was enhanced to show more detail and provide a better search experience.

Version 3.9 (Smith) (267 Contributors) improved the media experience and introduced live widget and header previews. The Visual Editor was improved for speed, accessibility and mobile use. Image and media improvements included adding the ability to upload images via drag and drop from desktop and image editing enhancement. Audio and video playlist support was added as well as Gallery previews from within the editor. Themes became browsable from the Appearance section.

2013 – Announcements: 3.6, 3.7, 3.8

Version 3.8 (Parker) (188 Contributors) introduced a new magazine style default theme called “Twenty Fourteen.”  The Admin panel was completely overhauled with a fresh modern look and new vector icons. Color schemes were also made available to be applied to the Admin experience. The Widget section was also streamlined for easier use.

Version 3.7 (Basie) (211 Contributors) introduced automatic updates for maintenance and security updates, a stronger password meter and enhanced language support and auto installation of language files.

Version 3.6 (Oscar) introduced a new default theme called “Twenty Thirteen,” built-in Audio and Video support, dynamic and scalable Revisions, improved Autosave and Post Locking. Audio and video improvements included native support for audio and video embeds, a built-in HTML5 media player, a new API for supporting metadata (such as ID3 tags) and enhancement to existing oEmbed providers Spotify, Rdio and SoundCloud.

2012 – Announcements: 3.4, 3.5

Version 3.5 (Elvin) introduced the new media manager and the new default theme called “Twenty Twelve” with focus on mobile display. Focus was also placed on the flow for uploading photos and creating galleries.  The Admin Dashboard saw the coming of a Retina-ready display with high resolution graphics.

Version 3.4 (Green) introduced the Theme Customizer and previewer, allowing to test and check theme revisions prior to applying them. The Media Library was extended to support using images to populate custom headers and to choose the height and width of the images. Image captioning saw improvements to support HTML. With this release, Twitter “Tweets” were made to format a nice display by dropping the URL into the editor. There were many developer improvements, including XML-RPC, a custom header API and performance improvements to WP_Query.

2011 – Announcements: 3.1, 3.2, 3.3

Winner of Infoworld’s “Bossie award for Best Open Source Software.”

Version 3.3 (Sonny) made WordPress more friendly for beginners with welcome messages and feature pointers. Improvements included a new drag and drop uploader, improved co-editing support, navigation and toolbar improvements and better touch support for iPad and other tablets.

Version 3.2 (Gershwin) made WordPress faster and lighter, this version upgraded minimum requirements to PHP 5.2.4 and MySQL 5.0.15, and introduced a new fully HTML5 default theme called “Twenty Eleven.” The Dashboard design was refreshed and the previously introduced Admin Bar saw additions. This release featured introduction of a Distraction Free Writing mode. The Comments Moderation screen was improved for approvals and replies. The update process was streamlined, making updates much faster with added stability.

Version 3.1 (Reinhardt) (180+ Contributors) introduced Post Formats and the Admin Bar.  A redesigned linking workflow was added to more easily work with existing posts and pages.  The beginnings of a streamlined writing interface were introduced. The import/export system was overhauled and there were many query improvements to enable performing perform advanced taxonomy and custom fields queries.

2010 – Announcement: 3.0

Winner of digitalsynergy’s “Hall of Fame CMS category in the 2010 Open Source.”

Version 3.0 (Thelonious) (218 Contributors) was a major release, it introduced custom post types, made custom taxonomies simpler, added custom menu management, added new API’s for custom headers and custom backgrounds, introduced a new default theme called “Twenty Ten” and merged former WordPress MU (allowing the management of multiple sites) to be part of WordPress Core, renamed to Multisite. Bulk plugin updates were further streamlined from the previous release. Theme developers saw introduction of new APIs allowing implementation of custom backgrounds, headers, shortlinks, menus, post types, and taxonomies without file editing. An initiative to add contextual help going forward saw its start.

2009 – Announcements: 2.8, 2.9

Winner of Open Source CMS Awards’s “Overall Best Open Source CMS.”

Version 2.9 (Carmen) (140+ Contributors) was a development intensive release introducing image editing, a Trash/Undo feature, bulk plugin updating, and oEmbed support allowing integrated 3rd party provider content to seamlessly integrate with content. There were also significant batch updating compatibility improvements, comment framework enhancement, editor upgrades, user profile, registration and automation improvements, gallery items usage across multiple posts introduction and better hooks and filters for excerpts, smilies, HTTP requests, user profiles, author links, taxonomies, SSL support, tag clouds, query_posts and WP_Query.

Version 2.8 (Baker) introduced a built-in theme installer and improvements to themes, widgets, taxonomies, and overall speed (including a new Widget API) (and drag and drop). There were significant speed enhancements relative to style and scripting. A new CodePress editor added syntax highlighting to the Dashboard based code editor. Screen Options were added to the Admin in order to customize user interaction with the items being used and the ability to filter out the others.

2008 – Announcements: 2.5, 2.6, 2.7

Winner of Infoworld’s “Best of open source software awards: Collaboration.”

Version 2.7 (Coltrane) which redesigned the administration UI to improve usability and make the admin tool more customizable. Version 2.7 also introduced automatic upgrading, built-in plugin installation, sticky posts, comment threading/paging/replies and a new API, bulk management, and inline documentation.

Version 2.6 (Tyner) built on 2.5 and introduced post revisions and Press This. A usability study was done on 2.5 over the summer, leading to the development of the Crazyhorse prototype, and the following release.

Version 2.5 (Brecker) was released with a new administration UI design by Happy Cog, and introduced the dashboard widget system and the shortcode API.

2007 – Announcements: 2.1, 2.2, 2.3

Version 2.3 (Dexter) offered tagging, update notifications, pretty URLs and a new taxonomy system. Core update notifications were introduced allowing users to better keep track of when new release updates were available. The jQuery version was updated bringing speed increases. canonical URL fixes were added and a new $wpdb->prepare() syntax support rolled out allowing for safer MySQL queries.

Version 2.2 (Getz) brought better Atom feed support and speed optimizations for plugins and filters. Widgets introduction laid the groundwork for moving additional features into design, which provided a base for plugin features extension. Protection was added on activating plugins, checking for errors prior to successful activation. phpMailer was added which also provided support for SMTP Mail. Database collation control and many code notation improvements were also part of this release.

Version 2.1 (Ella) introduced a new UI, autosave, spell check and other new features. Enhancements added ability to switch between content and code editor, setting pages as the front page, adding no-indexing to the entire site for search engine privacy, XML importing improvements and the addition of the private pages feature. MySQL queries saw an aggressive optimization and re-write. Other developer additions included new hooks and APIs, language improvements and pseudo-cron scheduling.

2005 – Announcements: 1.5, 2.0

Version 2.0 (Duke) was introduced with persistent caching, a new user role system and a new backend UI. WYSIWYG editing brought a better experience producing content which also included inline image, video and file uploads. Post previewing allowed to review posts before being made live on sites. Plugin hooks were enhanced to allow for features extension by plugin developers. Theme functions were introduced to enhance themes with code, similar to plugins.

Version 1.5 (Strayhorn) introduced a Theme system and featured the introduction of static pages, bring WordPress to be poised as a content management system. A new theme became available to showcase how the newly deployed Theme system could be extended and utilized. Hundreds of hooks were made available, allowing for integration of plugins to key parts of WordPress. The WordPress Plugin Repository was created allowing for a collaborative environment between Plugin Developers and users.

2004 – Announcements: 1.0, 1.2

Version 1.2 (Mingus) introduced plugins, hierarchically category support, OPML import and export as well as introductory language support. Features like automatic thumbnail creation, multiple update service pinging and password encryption also were highlights.

Version 1.0 (Davis) was the official 1.0 bringing browser installation, search engine permalinks, multiple category support, an intelligent upgrade process and import enhancement for moving from other systems to WordPress. Support was added to the Admin experience for editing posts and comments as well as the start of many other features to be improved on in the future.

2003 – Announcement: 0.7 (initial)

Version 0.7  Matt Mullenweg and Mike Little fork b2 and create WordPress. This initial release included a texturize engine, links manager, XHTML 1.1 compliant templates, a new administration interface, the ability to do manual excerpts and new templates.

2001:

b2 cafelog launched by Michel Valdrighi.

The only current officially supported version is the last major release of WordPress. Previous major releases before this may or may not get security updates as serious exploits are discovered.

Beta versions, nightly builds, and Subversion check outs are not supported on the WordPress.org support forums or on the WordPress Documentation.

If you are unable or unwilling to file bug reports, and help fix problems, please do not use anything other than the officially released versions.

Some folks in WordPress Slack might be familiar with unreleased versions, but it’ll be hit-or-miss, and no guarantee of support is provided.

Support Policy

Security updates will be backported to older releases when possible, but there are no guarantee and no timeframe for older releases. There are no fixed period of support nor Long Term Support (LTS) version such as Ubuntu’s. None of these are safe to use, except the latest series, which is actively maintained.

For the full list of WordPress Versions, refer to WordPress_Versions.

People are often confused about the differences between WordPress and WordPress.com. WordPress is the free, Open Source web publishing software project, owned by no one individual or company. WordPress.com is a hosted blogging service run by a company called Automattic.

WordPress

WordPress (sometimes called “WordPress.org” or “self-hosted WordPress” for disambiguation purposes), is software that you can download and install on any web host. It began in 2003 as a fork of b2/cafelog. Licensed by the GPL, you are free to use WordPress without restriction. Sites powered by WordPress may have a “Proudly powered by WordPress” credit, or they may have no credit at all. The absence of any mention of “WordPress.com” is a good indicator that it is a self-hosted WordPress instance).

WordPress.com

WordPress.com (a.k.a. “wpcom” or “WP.com”) is a for-profit hosted blogging service run by Automattic. WordPress.com launched in 2005, and is the largest WordPress install in the world. It is powered by WordPress, with some additional plugins and modifications layered on. Having “.wordpress.com” in the domain of the blog or the presence of a “Blog at WordPress.com” promo message or credits image can be used to determine whether a site is hosted at WordPress.com.

Overlap

What is the overlap between WordPress and WordPress.com? First, Matt Mullenweg is both CEO of Automattic, and co-founder of WordPress. Matt is involved with both WordPress and WordPress.com. Some WordPress contributors are also employees of Automattic. There are many more WordPress contributors, most of which have no connection with WordPress.com.

Development decisions about WordPress are made without specific regard to their impact on WordPress.com. Any special changes that WordPress.com needs are made on that side, by Automattic employees.

Additional resource

This video is an overview of the differences between WordPress and WordPress.com:

FAQ

Automattic’s relationship to WordPress?

Automattic uses WordPress to power WordPress.com, and it contributes back code and time to the WordPress project. It is a symbiotic relationship. It isn’t accurate to say that WordPress is Automattic’s product, or that WordPress came from Automattic. Indeed, the opposite is true — Automattic came from WordPress, and Automattic (through WordPress.com) exists as part of the vast WordPress community and ecosystem.

Why can’t I call WordPress.com just “WordPress”?

Because it isn’t clear what you’re talking about — the Open Source project, or the hosted blogging service. They are distinct, and statements about one aren’t necessarily true about the other. WordPress.com is its name. You wouldn’t call bit.ly, the popular link shortening service, just “bit,” would you?

Why doesn’t Automattic rename WordPress.com to something more distinct?

You’ll have to ask them. Likely, the downsides of a rebranding campaign would outweigh the benefits. The ambiguity certainly hasn’t been all bad. It makes it fairly clear to users that they can migrate their WordPress.com blog to a self-hosted WordPress install.

NOTE: WordPress core developers share a love of jazz music, and since WordPress 1.0, all major releases are named in honor of jazz musicians they admire.

Released Versions

Version 0.7

Version 1.0

Version 1.2

Version 1.5

Version 2.0

Version 2.1

Version 2.2

Version 2.3

Version 2.5

Version 2.6

Version 2.7

Version 2.8

Version 2.9

Version 3.0

Version 3.1

Version 3.2

Version 3.3

Version 3.4

Version 3.5

Version 3.6

Version 3.7

Version 3.8

Version 3.9

Version 4.0

Version 4.1

Version 4.2

Version 4.3

Version 4.4

Version 4.5

Version 4.6

Version 4.7

Version 4.8

Version 4.9

Version 5.0

Version 5.1

Version 5.2

Version 5.3

Version 5.4

Version 5.5