WordPress trunk is now very much in the …

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.

WordPress 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. is now very much in the alpha stage. A big custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. as well as some refactoring recently went in. The MU merge will begin soon. If you don’t want to be on the bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk., stick with the 2.9 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"..

Pingback: The merge begins - WPMU Tutorials
Alex M. 1:41 am on January 6, 2010

Do you expect lots of explodey? I run 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. on my blogblog (versus network, site) (updated hourly) and don’t mind if it’s down from time to time (I wanna help catch bugs), but if you think it’ll be broken 1/2 the time, I’ll svn switch until a little later in the development cycle.
- wpmuguru 3:33 am on January 6, 2010
  
  We’re going to try to avoid the explodey if we can. If things are going to be dicey, I’ll try to put out a heads up.
hakre 5:27 am on January 6, 2010

I would love to see a 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". for the mu merger. Looks for me a more propper way than just throwing on the head branch. Additionally I would have loved to see some more talk about that in the dev meeting.
- Alex M. 5:29 am on January 6, 2010
  
  Isn’t that the point of 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.?
  - hakre 5:32 am on January 6, 2010
    
    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. =/= 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".. just do a merge into an own branch based on current head then merge back if it’s in order. otherwise we need a commit freeze for all non-mu related things until mu codebase is merged in. oh yeah well, you can do all at once that will help us a ton 🙂
  - hakre 5:39 am on January 6, 2010
    
    another good argument for the merger-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". is that failure is an option — albeit an unlikely one. so if the merge fails current head is protected from that failure because the merger is more seperated from it.
- Peter Westwood 7:54 am on January 6, 2010
  
  A 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". is the perfect place to implement a big new feature if your not sure what version it will be included in.
  
  But you still have the cost of all the merging you have to do to keep the two in sync.
  
  For the merge of wpmu into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. it seems much more sensible to do it in 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. alongside other development as it is one of the core features of 3.0.
  - hakre 12:28 pm on January 6, 2010
    
    Indeed, not doing it into 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. would mean that an actual concept how to do the merge must exist. I just take the “just commit” approach as proof that such a concept just does not exist. I would at least like to have decent information upfront what the trunk will be confronted with in the next days and when this committing of WPMU code is over.
  - Peter Westwood 10:26 pm on January 6, 2010
    
    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. is for bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk. development code.
    
    The merge of mu into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is bleeding edge development code.
    
    We believe in commit early, commit often. This makes it easy for people to review changes and get involved.
Denis de Bernardy 2:45 pm on January 6, 2010

It’s looking scary already… Are we sure we don’t want to delay this until 4.0? 😉
Banago 4:54 pm on January 21, 2010

Cool stuff! Cannot wait to have MU on the single version. I really hope that will bring WP community a lot of advantages too.

Comments are closed.

Welcome!

Communication

Share this:

Site resources