WordPress.org

Make WordPress Core

Tagged: dev chat Toggle Comment Threads | Keyboard Shortcuts

  • Jeff Paul 8:06 pm on September 22, 2016 Permalink |
    Tags: , dev chat,   

    Dev Chat Summary: September 21 (4.7 week 5) 

    This post summarizes the dev chat meeting from September 21st (agenda, Slack archive).

    Reminders

    • Schedule: As of this meeting, we are 4 weeks from the final chance to merge in major features. This includes Twenty Seventeen.

    Bug Scrubs

    Components & Features

    • Twenty Seventeen (@davidakennedy, @melchoyce)
      • Announcement post, latest update
      • Maintainers are out travelling today, but #core-themes is active and they will be holding a meeting on Friday at 18:00 UTC
    • REST API (@krogsgard, @kadamwhite )
      • Latest update
      • API discussion is at 7 am Pacific on Mondays
      • Settings endpoints and meta support both have first-passes on them, which need internal review and some more testing before we ship
      • We have a path forward for passworded posts (password in the query string, eww, but only viable option), there really isn’t a way we can see to avoid sending them as a query param
      • Meeting tomorrow in #core-restapi at 21:00 UTC to go through open issues around non-trivial, conceptual issues in WordPress. REST API team will prepare summary of issues for component maintainers and/or lead devs to review, question, and help guide discussion towards consensus.
    • Media (@mikeschroder, @joemcgill)
      • Latest update
      • Moving our weekly meetings up to Fridays at 17:00 UTC starting this week
      • Unexpected change to media title behavior in WP 4.6.1 (#37989) – The main issue here was resolved, but there seems to still be some odd behavior affecting words being chopped off filenames with international characters. Could use extra eyes from anyone (along with @sergey) more versed in i18n. Regression on the attachment titles that we generate on upload all became URL encoded instead of reading like a normal title.
      • Media search doesn’t include file name (#22744) – Committed earlier this week. Please report any issues that come as a result.
      • Next step in improving the organization of the media library is to assess both the infrastructure and UI improvements that need to be made here. Prefer to include #design early in this process, rather than asking for UI feedback on development driven decisions, hope to be part of the #design chat agenda tomorrow
    • Customize (@westonruter, @celloexpressions)
      • Latest update
      • In this week’s meeting we developed a schedule for publishing make/core feature proposals/dev notes for the remaining primary 4.7 customize projects, working backward from anticipated time to commit after the proposal and current readiness:
        • Week of 9/19: Improving sliding panels UI (34391, @delawski)
        • Week of 9/26: A new experience for themes in the customizer (37661, @celloexpressions). Please review soon for any requested changes in direction or design.
          • Summary: The existing themes section in the customizer is replaced with a full-screen theme browser and installer… The UI is nearly identical to wp-admin/theme-install.php… The .org-based theme-install previewer is not accessible here because it is likely to cause confusion with its customizer-like interface and the resulting need to switch contexts back and forth… An overarching goal is to avoid switching in and out of the admin/frontend/customize contexts during theme installation and previewing, instead staying in the hybrid customizer context that provides a combination of frontend plus controls… On the technical side, this heavily leverages JS-templated customizer controls and scales nicely to hundreds of themes.
          • Visual:
          • Please comment on the ticket with your feedback as soon as possible, preferably with specific concerns/ideas and reasons.
          • @celloexpressions to check in with @karmatosed on user testing ahead of posting final feature proposal
        • Week of 9/26: Customize transactions (30937, @westonruter evaluating this week and might punt again)
        • Week of 10/3: Code-editing gateways, via CSS (35395, @johnregan3/@celloexpressions). Awaiting approval/feedback on the acceptability/ability to bundle the two proposed libraries in core, with feedback particularly needed from committers and anyone familiar with the Jetpack fork of CSSTidy.
        • Week of 10/10: Customizer browser history (28536, @westonruter)
    • I18n (@swissspidy)
      • User Admin Language (#29783) – almost ready, another review this week and will commit if no blocker pops up
      • Introduce a locale-switching function (#26511) – @ocean90 to do some benchmarking
      • Introduce some JavaScript i18n functions (#20491) – GlotPress side has a solid plugin for exporting translations as JSON files (assistance on testing would be helpful). Still tinkering with the WordPress side and would love to get some additional feedback there.
    • Editor (@azaozz, @iseulde)
      • No updates, but would love to figure out a way to get more user feedback that helps us set direction for the editor. Will look to add some Core questions to annual survey on WordPress.org. Otherwise will start with something in the beta tester plugin, biased audience but it’s one that exists, is more likely to opt-in, and will be more flexible.
    • HTTPS (@johnbillion)

    Open Floor

    • @pbearne on Add filters to wp_new_user_notification and wp_password_change_notification (#38068) – added a set of filters to allow us to override email messages send by the wp_new_user_notification and wp_password_change_notification functions. @johnbillion to review as it relates to work on notifications.
    • @danieliser checking for interest for core in a set of reusable templates, models & functionality for forms, tabs & modals
    • @ericlewis on Bulk actions: Reactivate bulk actions hook + add hander hook for all admin screens (#16031) – could use a review of the latest patch, looking to commit sometime in the next week
    • @dshanske still working through the Pings and Trackbacks component
     
  • Aaron Jorbin 3:30 am on September 21, 2016 Permalink |
    Tags: , , dev chat   

    Dev Chat Agenda for September 21 (4.7 week 5) 

    This is the agenda for the weekly dev meeting on September 21, 2016 at 20:00 UTC:

    If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

     
  • Aaron Jorbin 2:40 pm on September 15, 2016 Permalink |
    Tags: , dev chat,   

    Dev Chat Summary: September 14 (4.7 week 4) 

    This post summarizes the dev chat meeting from September 14th (agenda, Slack archive).

    Reminders

    As of this meeting, we are 5 weeks from the final deadline to merge major features.
    There are a lot of tickets in the milestone and owners / people who milestoned them need to make sure they are active and moving, or else punt. You can use this report see tickets in the milestone grouped by who moved it there:https://core.trac.wordpress.org/report/61.

    Components and features

    Twenty Seventeen (@davidakennedy, @melchoyce)

    Make sure to checkout both the Announcement post and the latest update. There is no formal meeting this week. Development has started on GitHub. Like many feature projects, it will live on GitHub until it is ready to come into SVN (within the next 5 weeks).

    REST API (@krogsgard, @kadamwhite, @joehoyle, @rmccue)

    Core patches, documentation, and reducing the issue backlog have been the primary focuses. There is a settings registry up (https://github.com/WP-API/wp-api-site-endpoints/pull/13) with a corresponding core patch (https://core.trac.wordpress.org/ticket/37885).

    Feedback is needed on #37885.  Please take a look.

    #38056 is needed for password posts. (update: it has landed).

    The next dev chat is Monday September 19 1400 UTC.

    Media (@mikeschroder, @joemcgill)

    • Still looking for feedback/testing on #22744, but planning to commit soon.
      • If you have a large media library, your help in testing would be particularly helpful.
    • @paaljoachim continued researching UI flows in other platforms and posted a bunch of screenshots in #core-images.
    • Joe shared an outline of what we’re trying to accomplish longer term here in#core-images and would like to talk more about it design side of things during the #design meeting tomorrow, if possible.
    • Still waiting to hear back from folks who were involved in starting up the Core Media Widget #32417 work, but travel has been an issue. Hopefully we’ll have a better update there next week.

    Customize (@westonruter, @celloexpressions)

    • @boone is thinking about/investigating ⁠⁠⁠⁠term_status⁠⁠⁠⁠ for #38015. We have some time to think about it, and could potentially use shadow/draft taxonomies as a workaround for #38014 in 4.7 if needed.
    • tracking the ability to add page stubs or create pages directly from the static front page controls along with this project to facilitate creating pages for initial site setup within the customizer. @westonruter is leading the way on #38013.
    • #34391 is a significant refactoring of code that themes and plugins are encouraged to extend. A corresponding make/core post will follow soon after.
      • Already working with some plugin, theme, and framework authors to minimize breakage.
    • We need some feedback now on #35395 – Custom CSS – @johnregan3 is making great progress.  Please check out the ticket.

    i18n (@swissspidy)

    • #29783 (User Admin Language): in good shape, but not much testing happening so far. We could do much more when #26511 is in core though…
    • #26511 (switch_to_locale()): needs some much needed performance testing. If anyone runs a large WordPress site, I could use your help!
      Also since there are some similarities with switch_to_blog(), I’ll open a new ticket to suggest adding a WP_State interface for such switching functions. Think WP_Site_State, WP_Locale_State, WP_Post_State (see #19572), etc. Not a blocker, but worth keeping in mind for future compatibility.
    • #20491 (JS i18n): I documented the current state in the tasks with responsibilities etc. As of tomorrow I’ll have more time to work on it (mainly on the GlotPress side of things). Also have been thinking about a switch_to_locale() function in JS via Ajax…

    Editor (@azaozz, @iseulde)

    • Post your wishlist items for the editor.

    HTTPS (@johnbillion)

    • Plan of attack for HTTPS work will be published on Make/Core.

    Open floor for tickets and any lingering 4.7 ideas.

    Please review and comment on these tickets:

     
  • Helen Hou-Sandi 5:25 pm on September 14, 2016 Permalink |
    Tags: , , dev chat   

    Dev Chat Agenda for September 14 (4.7 week 4) 

    This is the agenda for the weekly dev meeting on September 14, 2016 at 20:00 UTC:

    If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

     
    • Pascal Birchler 6:11 pm on September 14, 2016 Permalink | Log in to Reply

      I might not be able to attend today’s dev chat, so here’s an update on i18n:

      #29783 (User Admin Language): in good shape, but not much testing happening so far. We could do much more when #26511 is in core though…

      #26511 (`switch_to_locale()`): needs some much needed performance testing. If anyone runs a large WordPress site, I could use your help!
      Also since there are some similarities with `switch_to_blog()`, I’ll open a new ticket to suggest adding a `WP_State` interface for such switching functions. Think `WP_Site_State`, `WP_Locale_State`, `WP_Post_State` (see #19572), etc. Not a blocker, but worth keeping in mind for future compatibility.

      #20491 (JS i18n): I documented the current state in the tasks with responsibilities etc. As of tomorrow I’ll have more time to work on it (mainly on the GlotPress side of things). Also have been thinking about a `switch_to_locale()` function in JS via Ajax…

    • Ronald Huereca 6:24 pm on September 14, 2016 Permalink | Log in to Reply

      I’d like https://core.trac.wordpress.org/ticket/38024 discussed as I believe it to be a fairly major bug in regard to automatic updates for plugins and themes.

  • Jeff Paul 2:24 pm on September 12, 2016 Permalink |
    Tags: , dev chat,   

    Dev Chat Summary: September 7 (4.7 week 3) 

    This post summarizes the dev chat meeting from September 7th (agenda, Slack archive).

    Update on 4.6.1

    Updates on Components and Features

    • Media via @joemcgill
      • #22744 – a few approaches on this ticket that are pretty close, but some feedback that would be helpful
        • To enable searching for filenames, we have to add a JOIN for the meta table, which has performance implications
        • so a) we could use more eyes/testing and b) I want to make sure we’re ok to add this if we limit it to only the media library
        • We have a couple approaches in patches. The latest limits it only to the media modal and WP_Media_List tables.
        • on a site with ~14k attachments and ~18k posts, this change increased the main query time from 60.7ms to 187.6ms
        • Plan is to drop it in for including titles in library searches and see how that goes
      • Looking for interest in getting the media widget started back up
        • @sheri has expressed interest and it seems like previous efforts got fairly close. Would love to see folks interested jump back onto that project during this release.
        • discussion will be in our weekly meeting in #core-images on Fridays at 19:00 UTC. There is a jump-start post so people can comment there or jump into the #core-images channel.
    • Customize via @celloexpressions
      • Two items needing review:
        • 1) ability to preview terms in the customizer, which would enable users to build menus incorporating their new taxonomy term structure on initial site setup in the customizer. See #37914 and #37915. We need to come up with a plan with those interested in the taxonomy component, and @boone in particular. First step there is to decide if we want to try to target 4.7 for first steps there.
        • 2) #37661 needs feedback. Working on a user testing plan together with @karmatosed soon. Looking for specific feedback or testing.
    • REST API via @krogsgard
      • Notes from Monday’s meeting
      • Calls for help would be participation in our next weekly meeting, 1400 UTC on Monday, and a bug scrub 1400 UTC on Thursday, both via #core-restapi
      • some in-flight work this week that’s being a bit delayed by the participation of Ryan and Joe in A Day of REST
      • We have big documentation needs in the v2 docs repo if anyone wants to play along, especially anybody who wants to set up a multi-language-code-snippet thing that we could use
      • meta and options are both moving well but we’ll need to start getting beyond theory and into code pretty soon
      • We really, really want to talk to component maintainers! It’s my job to reach out to you all, and you can also reach out to me (@krogsgard).
    • I18N via @swissspidy
      • #26511 (switch_to_locale()) and #29783 (User Admin Language)
        • Those are currently in development and after I upload new patches today/tomorrow, I’d love to see some testing.
        • Think of possibilities like: The admin bar is shown in Dutch while the rest of the site is shown in English.
      • #20491 (Introduce some JavaScript i18n functions)
        • We want to make translating strings in JavaScript files easier. Like in PHP files, one should be able to use gettext functions to translate strings. This involves changes to the translate.wordpress.org platform and therefore requires thorough discussion, planning, and testing.
        • After tackling this topic many times and attending the GlotPress meeting yesterday, it’s clear that it’s a task covering not just 1 release. Thus, we’ll likely have to do regular meetings here in Slack to get there.
    • Fields API via @sc0ttkclark
      • looking into slimming down our Fields API proposal into a MVP form for our core proposal
      • blocked by lack of time because i’m also lead organizing WCDFW this month
      • I could use lots of eyes on it, we want to identify anything that might be out of scope, as well as look into what our plan will be for the Javascript side of things for fields like the Media modal
    • #36964 (Show/hide the tag-cloud on `edit-tags.php` admin pages using a filter) via @ramiy
      • it has a patch, ready to be commited
    • #17817 (do_action/apply_filters/etc. recursion on same filter kills underlying call) via @ocean90
      • Landed!
    • #37198 (Use `WP_Term_Query` for `wp_get_object_terms()`) via @flixos90
      • Would like some eyes on this.
      • The patch is two months old now, but generally worked and passed unit tests when I did it – I think feedback is needed before this moves forward though.
    • Topics & folks with no updates this week:

    Twenty Seventeen

    • Announcement post is up
    • This will be a call for help on both the theme and theme API fronts as noted last week, and thoughts on what sorts of theme API things will be needed to support the theme (there will be a number noted in the post).
    • For a little bit of a preview, some of the things that should be looked at are better page-on-front flows, making it easier to figure out where to edit something while live previewing (aka customizer), and how we can help people see how the theme can really serve their needs well (when relevant).
    • There will be *a lot* of opportunity for UX and UI when it comes to the core side of things, and of course front-end development with the theme itself. And lots and lots of our traditional PHP and JS development.
     
  • Jeff Paul 1:02 am on September 2, 2016 Permalink |
    Tags: , dev chat,   

    Dev Chat Summary: August 31 (4.7 week 2) 

    This post summarizes the dev chat meeting from August 31st (agenda, Slack archive).

    Holidays & Scheduling

    • Reminder to announce meeting moves or cancellations (e.g., Monday is US Labor Day holiday, Monday after is Eid al Adha)

    Update on 4.6.1

    #36335: Autoloader and #37699: Globals

    • Discussion framing: see these as being feature projects in their own right, examples of when features can’t be actual plugins and why it’s better to think of them as projects. How can these be worked on effectively?
    • Discussion:
      • New project on GitHub that’s a clone of the WP Git repo
      • grunt patch allows you to use GitHub PR URLs, which can help facilitate testing for people that prefer using SVN or are using SVN for their trunk installs.
      • Trac + SVN workflow seems to work best when we’re dealing with patches and discussion leading to an individual commit; is probably a pretty poor option without some additional tools.
      • Creating feature branches for wide-ranging work seems to be a better fit and allows for less churn of the code in trunk at the same time as other major work.
      • Nice to review & collaborate on a big feature on a GitHub feature branch as opposed to wrangling conflicting and amending patches on Trac
    • Suggestion to @wonderboymusic: fork @jorbin‘s GitHub mirror, use GH issues and develop in various branches as makes sense (or even separate forks entirely if issues become unwieldy across very different projects), and use PRs to run existing CI setup. PRs can then be used as patches in grunt patch
      • If treated as a feature project, all of that project’s management happens wherever the lead feels best serves that project. There should also be weekly meetings with updates posted on Make/Core. @wonderboymusic to determine a meeting time and post about it next week.
      • @wonderboymusic@helen in agreement on approach; GitHub repo created
    • Related question: How do we determine what sort of tasks should be feature projects? Who decides that? And when?
      • Some things to think about – is it a lot of churn? Does it need to span multiple releases and/or is it a “done when it’s done” process? Is there a lot of design and user testing involved? They exist whenever somebody has a thing they believe belongs in core and wants to run with it in that way. Getting feedback is an evolving process.

    4.7 Project/Feature Proposals

    • Goal: come out of this with the start of a list of projects and a point person for that project, to be fleshed out with more participants and meeting times over the next week.
    • @johnbillion – HTTPS
    • @celloexpressions – Customize component project & owner
      • Create page-based nav menus without leaving live preview – #34923@celloexpressions (follow up tickets forthcoming)
      • A new experience for themes in the customizer – #37661@celloexpressions
      • Code-editing gateways, via CSS – #35395@johnregan3
      • Customizer browser history – #28536@westonruter
      • Refactoring sliding panels UI – #34391@delawski
      • (maybe) Customize transactions (with no UI) – #30937@westonruter
      • will track all of the Customize projects with the weekly Customize component meetings and Make/Core posts usually posted on Thursdays starting this week
    • @krogsgard – REST API
      • had a productive start on Monday and will have a summary up shortly
    • @boonebgorges – #20875
      • work with cache drop-in authors so that we can start leveraging across WP
    • @davidakennedy – #19627
    • @helen – there needs to be a dedicated theming API/support team because there will be a Twenty Seventeen; actual details on that next week. There will need to be really robust teams on both the theme and theme support pieces, likely with subteams even.
      • @karmatosed: splitting core themes as a bucket for all theme into, core themes and theme functionality
      • @helen: noting that theme functionality will spill over into other components (media seems incredibly likely)
      • @themiked: interested in theming work, on the API/support side if that’s whats needed
    • @joemcgill – Media focus candidate & owner; will shepherd these through regular #core-images meetings
    • @azaozz – will publish “4.7 editor wishlist” by the end of the week
      • to include Nonce refresh/saving without page reload, and few others
    • @sc0ttkclark – Fields API

    Ways YOU Can Help!

    • Please comment below if there are things that didn’t get mentioned that you’d like to lead.
    • Design help and user test coordination (alongside @karmatosed) desired on #37661 by @celloexpressions, please respond if you’re open to help on this.
     
  • Helen Hou-Sandi 5:39 pm on August 31, 2016 Permalink |
    Tags: , , dev chat   

    Dev Chat Agenda for August 31 (4.7 week 2) 

    This is the agenda for the weekly dev meeting on August 31, 2016 at 20:00 UTC:

    • General reminder: as holidays or other conflicts come up, be sure to announce meeting moves or cancellations. For instance, next Monday is the US Labor Day holiday and the Monday after that is Eid al Adha.
    • Update on 4.6.1.
    • #36335: Autoloader and #37699: Globals – what could and should happen in order to be effective and move forward?
    • 4.7 project/feature proposals: who wants to work on what?
    • Triage of tickets marked early for 4.7 (milestoned and unmilestoned).

    If you have anything to propose to add to the agenda, please leave a comment below. See you there!

     
  • Jeff Paul 4:39 pm on August 25, 2016 Permalink |
    Tags: , dev chat,   

    Dev Chat Summary: August 24, 2016 

    This post summarizes the dev chat meeting from August 24th (agenda, Slack archive).

    4.6.1 Schedule

    4.7 Personnel and Schedule

    • @jorbin (engineering/development focus) & @jbpaul17 (PM focus) will be release deputies for 4.7
    • Full release schedule can be found at https://make.wordpress.org/core/version-4-6-project-schedule/
    • The scheduled release date is December 6.
    • Due to WCUS & US Thanksgiving holiday, we will have to treat RC as a true Release Candidate
    • There is no “merge window”, testing & feedback should be continuous before merge consideration

    Potential Focus Areas

    • Many wishlist comments are specific developer-facing features as well as better media findability/organization, easier plugin management, and the initial theme setup experience
    • New default theme (aka Twenty Seventeen) likely, but to be confirmed within the next week or two
    • REST API content endpoints (posts, terms, comment, users, and their associated meta) to get defined roadmap for 4.7 delivery plus future roadmap to full management and admin API coverage (potential approach)
      • the next meeting will be August 29 at 23:00 UTC, where this will be further discussed
      • @krogsgard aiming to write spec for each item in the list by next meeting, open to acting as PM for this focus area
      • looking for a few committers with knowledge around the API to guide the process with a permanent or lead as their buddy
      • looking for review from outside WP community
      • will require documentation coverage for builders and consumers
      • Core endpoints will need to be reviewed by their respective component maintainers

    Open Forum on Focus Areas

    • “find your media more effectively” (#22744)
    • taxonomy (aka media tagging) UX+UI work for assignment and filtering mechanisms
    • “find an accessible multi-select/autocomplete/tagging helper”
    • “smarter defaults”
    • Eliminating usability dead-ends in the customizer (#34923, #35395, #37661)
    • further refinements to the updates flow continuing from 4.6
    • low-fi mockup and testing of metabox for different publishing possibilities (including existing examples)
    • resolve some ancient annoying issues (e.g., #17817)
    • Content Authorship in Menus, with Live Preview
    • dashicons as svg sprite (Make/Core Post)
    • document dynamic hook aliases in core (finally) + adding DevHub support
    • initial theme setup experience

    Teams and Weekly Updates

    • Teams are the contributor groups that form around components and major work items (e.g. features and big API changes)
    • Will continue to identify those Teams and a “spokesperson” for each
    • Teams should have a weekly scheduled meeting and a weekly update posted to Make/Core
    • @helen to continue the tradition of weekly jump start posts, so there will be a reminder of Team meetings each week

    Wishlist Items

    Bug Scrubs

    • Everyone is empowered to run a bug scrub (can be component based, or based on any other ticket report)
    • A post with information on how to run a bug scrub and who is empowered to do it (hint: it’s you) will be published on make/core soon
    • Bug Scrubs are a great experience in running a meeting, writing good responses, and building confidence in making those do-or-punt decisions
    • You do not need to be a dev to run a bug scrub, @hugobaeta and the design team has done some great scrubs
    • You don’t need to be a committer to run them, @chriscct7 has done some incredible scrubs on ancient tickets
    • “If 5 new people that have never run a bug scrub or other core meeting before, run one this release: I will write and record a parody of “No Scrubs” by TLC, but about Bug Scrubs.” — @jorbin Π
     
  • Dominik Schilling (ocean90) 5:45 pm on August 10, 2016 Permalink |
    Tags: , , dev chat   

    Weekly Dev Chat Agenda for August 10 — Sixteen Weeks Later 

    This is the agenda for the weekly dev meeting on August 10, 2016 at 20:00 UTC:

    If you have anything to propose to add to the agenda, please leave a comment below.

    See you in the chat!

     
    • Engine44 7:04 pm on August 19, 2016 Permalink | Log in to Reply

      Hi,

      Even though I am just beginning to learn PHP, I am interested in helping out. Although, I need some help in setting up my Slack account with WP. I’ve gone through the recommended procedures but have been unable to get a Slack invite.

      Thanks,

      Bob Brooks

  • voldemortensen 4:29 pm on August 4, 2016 Permalink |
    Tags: , dev chat,   

    Dev Chat Summary: August 3, 2016 

    Current status of WordPress 4.6

    • The 4.6 branch was created this week.
    • RC2 was scheduled for today, but because https://core.trac.wordpress.org/report/6 has so many open tickets its being delayed by 24 hours.
    • The first draft of the About page was committed today. Please help review it to make it ✨ Shiny ✨
    • @hugobaeta is looking for feedback on the images he’s created for the About page. The feedback will be heard and discussed in the #design weekly chat on August 4th, 2016 at 20:00 UTC.

    Schedule for the next 13 days

    The schedule is as follows:

    • August 10 is RC3 with the hard string freeze. The about page must be finalized by then.
    • August 12 will be code freeze. Everything should be done by this date. Only version bumps and the video should committed after this.
    • August 15 is the dry run for WordPress 4.6. We’ll check everything, prepare w.org, do a dry run for release day, and with @davidakennedy and @karmatosed we’ll release the new versions of our default themes as well.
    • And well, August 16, 2016. WordPress 4.6!

    About page

    As already mentioned, a first pass is committed. Check your dashboard and let us know what you think. Maybe ask some friends who aren’t involved in the release since that’s our target group.

    Call for volunteers

    The call for future release leads has been published. Leading a release can be a rewarding challenge. If you have questions, feel free to ping @jorbin or @helen. Everyone interested, please express it on the post, pinging @jorbin or @helen isn’t enough. They are more so available for answering questions. https://make.wordpress.org/core/2016/08/01/release-leads-call-for-volunteers/

    Component announcements/updates and Open discussion

    Currently the contributor handbook is lacking in documentation in regards to contributing via git. Core has supported git contributions for over 2 years. If you have a git work flow, use git, or have git knowledge in general, please consider looking over https://make.wordpress.org/core/handbook/contribute/ and adding docs where appropriate. Please remember that supporting git does not mean using GitHub.

    Find full chat logs here: https://wordpress.slack.com/archives/core/p1470254406001902

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Skip to toolbar