Title: Version Confusion Last modified: August 18, 2016 --- # Version Confusion * [sicro](https://wordpress.org/support/users/sicro/) * (@sicro) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/) * After the version jump from 1.3 to 1.5, I am getting a bit confused as to where current nightlies are at, or rather, where WP is heading for the next stable release, which is currently still at 1.2.2. * I read the stuff about not being able to give a full feature list or roadmap for the next stable version, because things where changing so fast. But surely someone must have an idea about what the next WP is going to include or exclude. I mean exclusion as a positive thing to counter feature bloat – after all there are always plug-ins. A good plug-in API is probably a better feature than most hardwired features you could add. * I read, that the version jump from 1.3 to 1.5 was done because so much of the code was rewritten. Wouldn’t it have been better to fork the code and start a WPII, since now 1.5 is so far removed from the original 1.2? * While WP 1.5 is already collecting prizes, which suggests it’s nearing completion, there is no release candidate or beta version, instead there’s news that a team of four (forgot the names) is going to totally redesign the backend admin-panel. Nice to hear, but now I wonder is this still for 1.5 or are they already thinking about 2.x. * Basically I just want to know, when is the next stable release expected and what will it have under it’s bonnet. * — sicro Viewing 8 replies - 1 through 8 (of 8 total) * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-141520) * “Wouldn’t it have been better to fork the code and start a WPII, since now 1.5 is so far removed from the original 1.2?” * That’s why they changed it from 1.3 to 1.5. [http://wordpress.org/development/2004/12/version-skip/](http://wordpress.org/development/2004/12/version-skip/) * v1.5 will be released on the upcoming birthday of a great Jazz legend. [http://blog.nuclearmoose.ca/archives/2005/01/27/the-inside-scoop/](http://blog.nuclearmoose.ca/archives/2005/01/27/the-inside-scoop/) * What will be under its “bonnet”: [http://codex.wordpress.org/Version_1.5](http://codex.wordpress.org/Version_1.5) * [NuclearMoose](https://wordpress.org/support/users/nuclearmoose/) * (@nuclearmoose) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-141524) * Code is generally forked when another team of developers wants to take the software in a completely new direction. Version 1.3 to 1.5 is simply an evolution of the code. To fork it would be to change the goals and ideas of the main branch, and while the code is improving, the main concepts and ideas and philosophy of WordPress has not changed. * The re-design of the backend panel is simply a small group of community members wanting to add value to the product in their own way. WP 1.5 has already been through the beta version and is now in gamma. You can access this version through [http://wordpress.org/nightly/](http://wordpress.org/nightly/) . WordPress 1.5 did not collect any prizes…it was version 1.2.2 which was awarded the Ars Technica award. MacManX gave you some good links to check out. Maybe with some research, some of your questions will be answered and some of your assumptions will be changed. If you have any more questions, don’t hesitate to post them! 🙂 * Thread Starter [sicro](https://wordpress.org/support/users/sicro/) * (@sicro) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-142084) * macmanx: Thanks for the links. I think I had already looked at them at some point individually, but reading them together cleared up some of the confusion. So a final 1.5 is expected for july/august – great. I still think the codex.worpress. org site is a little confusing with all the 1.3(strikeout)/1.5 thrown in there. I also don’t understand why they used mediawiki for the codex and phpwiki for support. Makes the codex wiki look less official. * NuclearMoose: Still seems a funny move to abort development on a 1.3 branch and then continue on 1.5. The 1.2.2 although stable would have deserved a clean- up and re-release as a final final 1.3 (stable). Something as “dramatic” as a total re-write of your codebase would then merit a proper 2.0 – but that is just my humble opinion. You say that 1.5 is now in gamma, but just one look in the bugtracker suggests otherwise, there seem to be quite a few mayor bugs still open. Anyway – I can wait for a final release and I am looking forward to it. About the re-design of the backend panel – will that go into the final 1.5 or is this a fork of the current development? * [Mark (podz)](https://wordpress.org/support/users/podz/) * (@podz) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-142085) * July/August ? No. When it is ready 🙂 * phpwiki was the original wiki. WP ‘outgrew’ it, and mediawiki was selected as the tool to replace it. mediakwiki (aka Codex) is the official site for when WP 1.5 is released. It is currently being populated with lots of useful information. * Nothing was aborted. The devs simply looked at the code and realised just how much had been added. Even today, Matt has made the observation that he has been using latest code for so long he has forgotten what 1.2.x looks like – and I would agree. * And if you mean the Shuttle project, that’s a matter for the developers of that and the developers of WP. * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-142090) * Yes, where did you get July/August from? It says, “v1.5 will be released on the upcoming birthday of a great Jazz legend.” Not all Jazz legends were born in July and August. * [NuclearMoose](https://wordpress.org/support/users/nuclearmoose/) * (@nuclearmoose) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-142093) * [@sicro](https://wordpress.org/support/users/sicro/), Since when does “gamma” NOT mean that there are no bugs to fix? Since when does “official release” NOT meant that there are no bugs to fix? :o) * As for the admin panel work, as Podz and I both said, that is being done by community members, and is not a fork of WordPress. * [trendsurfer](https://wordpress.org/support/users/trendsurfer/) * (@trendsurfer) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-142094) * What does “gamma” even mean … does that mean it’s at a “no new feature” code freeze? * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-142096) * It’s greek alphabet. Alpha, beta, gamma, delta, epsilon, and so on. It just means that we’ve passed alpha and beta and are probably nearing the final release. * [http://en.wikipedia.org/wiki/Greek_alphabet](http://en.wikipedia.org/wiki/Greek_alphabet) Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘Version Confusion’ is closed to new replies. * In: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) * 8 replies * 5 participants * Last reply from: [James Huff](https://wordpress.org/support/users/macmanx/) * Last activity: [21 years, 4 months ago](https://wordpress.org/support/topic/version-confusion/#post-142096) * Status: not resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics