The release cycle for WordPress 3.6 isn’t going…

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

The release cycle for WordPress 3.6 isn’t going to start until January, but we can of course start to drop in some early things before then. (This worked out nicely before the start of 3.5.)

With that in mind, I have added jQuery 1.9 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 to trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. It comes with a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party for deprecated/removed features, and this migration plugin issues warnings in the console so we may fix them. Yes, we are likely to ship the migration plugin in 3.6 final; that’s why it exists. But for now, we should aim to fix anything not only outright broken in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but also any warnings. (There are a lot of them.)

For more, see the jQuery announcement post and the WordPress core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., #22975.

A side note: If you are using the WordPress Beta Tester plugin and wish to go back to the 3.5 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"., you can do so by changing the update stream setting from “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk. nightlies” (which is currently 3.6-alpha) to “Point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. nightlies” (which is currently 3.5.1-alpha) and then downgrade. Of course, we’re happy to have you testing the 3.6 branch, which will be kept fairly stable throughout its development.

#3-6, #jquery

Eric Mann 2:51 am on December 18, 2012

I like the idea of the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party … but I’m hesitant shipping any library that includes “BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.” in its version number. What’s to say parts of the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. won’t change by the time 1.9 is finalized? Not to mention the possibility of shipping bugs with our own release…
- Japh 3:13 am on December 18, 2012
  
  Most likely something that’s betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. now, will be stable by the time we’re ready to ship it. It makes more sense than going with the current stable and shipping that even after it’s out of date, or switching further through the dev cycle and not taking full advantage of new features.
- Andrew Nacin 5:06 am on December 18, 2012
  
  Sorry, I should have mentioned that jQuery 1.9 is due out in January, well before 3.6 would even be in betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process..
  
  We strive to always ship the latest of packaged external libraries. By being good citizens and dropping pre-release packages into our own trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision., we contribute greatly to the upstream project while also ensuring there *won’t* be bugs with our own release.
moebiusmania 9:05 pm on December 27, 2012

hi, there is any possibilities of having the $ alias for jQuery by default in 3.6?
- Andrew Nacin 3:44 pm on January 10, 2013
  No, likely not. jQuery.noConflict() — used for historical reasons because of potential conflicts with other libraries, primarily Prototype — also happens to enforce better code. You can still use $ in code, you just have to be smarter about it:
```
jQuery(document).ready( function($) {
   // You can use $ in here
});
```
  Or:
```
(function($) {
   // You can use $ in here
})(jQuery);
```

Comments are closed.

Welcome!

Communication

Share this: