Dev chat summary 3/30/2011

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.

3.2 check in:

Westi working on https://core.trac.wordpress.org/ticket/16827
Rboren pushed 3.1.1 this week, shifting to 3.2 now
Azaozz working on full-screen editing for Visual mode. Mini version of TinyMCE has no buttons or toolbars, but keyboard shortcuts work. Possible hidden/floating toolbar up top for some buttons. Will put out as 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 soon to begin testing/refining.
Pete Mall tending to multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site tickets that got pushed to 3.2.
Sivel and dd32 working on HTTP API. Got https://core.trac.wordpress.org/ticket/16236 in, have another dozen or so tickets active, anticipates “fairly large reworkings of the HTTP API in 3.2, mainly because we have been finding a lot of bugs and limitations”
duck_ pushed WordPress importer 0.4 yesterday, will be moving to 3.2 stuff soon (has a kses performance 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. in the pipeline)
No one else had anything to report on 3.2 progress

#dev-chat

Mark McWilliams 5:35 pm on March 30, 2011

If you go with https://core.trac.wordpress.org/changeset/17572 then I do believe it was only 3.1.1-RC1 that was tagged, it’s not actually been pushed out yet; but do correct me if I’ve missed something! 😀
- Jane Wells 5:39 pm on March 30, 2011
  
  Sorry, yes, it’s RC1. Not being touched though, unless someone finds a problem before release, so the shift toward 3.2 stands.
  - Mark McWilliams 5:46 pm on March 30, 2011
    
    Fair enough, it just sounded like 3.1.1 was out when it isn’t (yet).
- Ramoonus 10:25 am on March 31, 2011
  
  there it is;
  https://wordpress.org/wordpress-3.1.1-RC1.zip
Rami 7:20 pm on March 30, 2011

hi, how do we add this solution (https://core.trac.wordpress.org/ticket/16999) to the next version?
Joseph Scott 10:06 pm on March 30, 2011

Bummed I missed the chat this morning, there are some XML-RPC tickets that I’d like to get in for 3.2. I’ll try to pull together a list and review them in more detail during this week so that I’ll have a more detailed list to talk about next week.

Comments are closed.

Welcome!

Communication

Share this: