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.

Jen 2:57 pm on September 10, 2009

Topic suggestion for Sept 10 chat?

Jeffro 3:38 pm on September 10, 2009

I’d like to know if we could talk about the way releases are handled on the development blogblog (versus network, site). Taking a look at posts in the past regarding releases, the display of information, links to changesets or the lack thereof are all over the map. I think it would be beneficial for the team to share a template to use for Release type posts on the dev blog.

One other thing I wanted to know. Why is it that typically, to upgrade WordPress you need to upload the entire package even if just a few files were changed? For those folks where auto upgrade does not work and they do not want to wait for 20 minutes to upload the WordPress package, is it safe to just upload the changed files to perform the upgrade? This ties into my first discussion point.
- Jane Wells 3:46 pm on September 10, 2009
  
  “To share a template to use for Release type posts on the dev blogblog (versus network, site)” implies that there’s a template to share, which there isn’t. 🙂 Announcement posts are written individually and tend to vary in style based on what kind of release it is and who’s writing it. Matt’s posts are chatty and highlight the headline features, Ryan’s posts are practically haikus that link to the .zip, etc. I agree it would be good to have a set of information that is included each time, though, for whichever author to check against. Not sure if this needs to be a discussion point in the chat, though… might make more sense to put together a list of items to include, post it here, and invite feedback, especially since all the announcement authors won’t be in the chat today.
  
  There have been past releases where the announcement says you can just upload/overwrite specific files.
  - Dougal Campbell 3:09 pm on September 11, 2009
    I’m still drafting out a blogblog (versus network, site) post with many ideas for improving (I hope) community information and such. But just a quick note of what I think about regarding a “template” for releases:
    
    In each new feature release, there are changes in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. along these lines:
    
    new functions added
    
    existing functions modified (new arguments? return type changed? side-effects?)
    
    existing functions deprecated
    
    deprecated functions removed
    
    And where I say “functions” you could also substitute “classes”, “files”, “action/filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.”, and “global variables”, really. Fortunately, the first item is most common, and the other three cases are relatively infrequent.
    
    In order to help the third-party 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/theme development community stay up-to-date with changes in core, I think it is very important that these changes are documented in a standard fashion. Currently, we pretty much just have to keep our eye on changes in the SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. repo and/or TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and hope that we don’t miss something important. I’d like to us to have a known place where one could see these sorts of internal technical changes detailed in a formal way.
    
    Is there a way to automate it? I don’t know if there’s an existing tool for it, but at least some of it *could* be automated. It shouldn’t be hard to automate detection of new functions, classes, and files. And deprecation tagging should be easy, too. Detecting changes to existing functions could at least be partially automated, if it’s something obvious that affects the @param or @return tags in the phpdocPHPDoc (docblock, inline docs). Other changes (like a new global variable related to a new feature) might have to be documented manually. And of course, when I say that automating some of these things should be “easy”, I mean compared to trying to track them by hand and write it all up at release-time. 🙂
    
    BTW, I wish I could participate in the dev IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. chats, but they take place right around the time that I’m trying to wrap up work and get ready to head home, and my family is a higher priority 🙂
- scribu 5:19 pm on September 10, 2009
  
  For the second part, there was some discussion on downloading only changed files. Not sure if there’s a ticketticket Created for both bug reports and feature development on the bug tracker. on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. for it though.
- Mark Jaquith 8:20 pm on September 10, 2009
  
  There’s a way to do this in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., but it’s not immediately obvious. I can share in the chat.
- Dougal Campbell 8:53 pm on September 10, 2009
  
  It’s fine that various people do their own writeups about releases in their own style.
  
  But I think that there could be some value to codifying/formalizing some sort of “official announcement style”, even if it is posted separately (Codex?), and merely referenced in the other announcments.
  
  This is something I’ve been kicking around in the back of my brain for some time now, and there are hints of it in the postings I’ve made recently on wp-hackers, my own site, and in comments elsewhere, regarding the recent worm incident. I’m working on another blogblog (versus network, site) post about it now.
  
  This isn’t the place for a lengthy discussion about it, however. After I finish putting my thoughts down, I’ll post a note about it on wp-hackers, and I’d like to see some more discussion there about the pros/cons/costs/benefits of formalizing some release procedures and information.
  - Jeffro 9:04 pm on September 10, 2009
    
    Ok, guess I should get on the ball and rejoin the hackers mailing list.
scribu 8:01 pm on September 10, 2009

What’s happening with the GSOP projects? MPTT and the Search 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. especially.
- Alex (Viper007Bond) 8:02 pm on September 10, 2009
  
  Search: https://wordpress.org/extend/plugins/search/
  
  Been using it on my blogblog (versus network, site) for a while. Works great.
- Jane Wells 8:14 pm on September 10, 2009
  
  I’m getting updates on integration from all the GSoC mentors, but doubt I’ll have them all by today’s meeting. When they all come in, there’ll be a summary post on the dev blogblog (versus network, site). Held off on posting about it so we could say what was happening with each one (as opposed to just saying they were finished).
Pingback: WordPress Dev Chat For 9-11-09

Comments are closed.

Welcome!

Communication

Share this: