Tag Archives: 4.8.1

Jeffrey Paul 3:48 am on July 7, 2017
Tags: 4.8.1, , ,   

Dev Chat Summary: July 5th (4.8.1 week 3)

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

4.8.1 planning

  • #40907 is committed 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., but needs user testing
  • #40951 has a good 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., but not committed yet and needs user testing
    • Main holdup is the best use of pointers (or another notice mechanism) to inform users to use the Custom HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. going forward for adding arbitrary HTML
    • Another possible use of pointers is when a user pastes HTML into TinyMCE, to correct years of pasting into the Text widget’s textarea
  • Aiming to make a 4.8.1-alpha release build to make it easier for those testing, will also note testing steps on respective tickets
  • Will schedule 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. scrubs next week & post those times separately to Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.: image permissions model

  • Issue originally described in WP-API GitHub repo Issue 1987
  • Relates to #37186 and #17255
  • Will continue discussion in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., also in detail in upcoming Media component meeting

Editor

  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ is now at v0.3
  • As folks help test, please note the Gutenberg version when creating an Issue in the GitHub repo

General announcements

#4-8-1, #core, #dev-chat, #summary

Jeffrey Paul 5:08 pm on July 5, 2017
Tags: 4.8.1, , ,   

Dev Chat Agenda for July 5th (4.8.1 week 3)

This is the agenda for the weekly dev meeting on July 5, 2017 at 20:00 UTC:

  • 4.8.1 planning
  • Customize: Rich Text Widget updates
  • REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.: image permissions model
  • General announcements

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!

#4-8-1, #agenda, #core, #dev-chat

Jeffrey Paul 5:18 am on June 29, 2017
Tags: 4.8.1, , , , ,   

Dev Chat Summary: June 28th (4.8.1 week 2)

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

4.9 ideas

4.8.1 planning

  • #40951 & #40907 will be coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to the 4.8.1 release being targeted around the last week of July
  • General 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. scrub to be scheduled after the 4th of July holiday on the 4.8.1 milestone
  • Component maintainers please review your 4.8.1 milestone and puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) to Future Release / 4.9 as necessary
  • Reminder that we are “approaching 4.8.1 tickets as more traditional regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. types of issues”

Editor update

Customize update

  • appreciate more people testing 40951.3.diff
  • also appreciate testing of the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. 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. (see #40907)

REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. update

  • had a lot of new docs contributions at WCEU contributions day
  • have some momentum and hope to build upon it in coming weeks

Dev chat coordination

  • @jbpaul17 looking for 1-2 others out there to help run the weekly dev chats similar to how the Core Weekly Updates are split up
  • A great way for product/project management or otherwise non-engineers to help contribute to WordPress Core
  • Please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @jbpaul17 if you have interest in helping out!

New contributor bug scrub/open office hours

  • idea is a weekly bug scrub/open office hours focused on new contributors
  • would include tickets tagged good-first-bug and any tickets new contributors wanted to work on
  • Likely to schedule for Wednesdays at 19:00 UTC
  • @adamsilverstein, @welcher, @stevenkword, & @flixos90 to help run the meetings
  • Please ping @adamsilverstein if you have interest in volunteering as well

General announcements

  • @m1tk00: looking for help with the Gallery Widget in the Customizer regarding the edit button
    • need to know how to send the already selected ID’s, when someone wants to edit the gallery
    • will ping @obenland or @timmyc in #core-customize for help
  • @enricosorcinelli: #21676 patched and awaiting review, how to get it more attention?
    • added needs-testing to the ticketticket Created for both bug reports and feature development on the bug tracker., will ping @obenland as Themes component maintainer to review
  • @pbiron: would like to start a “feature plugin” project to work on rewriting the exporter
    • would like to rework ALL of the XML related code in core (e.g., using XMLWriter instead of echo statements, etc)
    • using XMLWriter and with some pretty drastic changes to the WXR markup
    • should be putting the 1st version up on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ in few days
    • also written an XML Schema for WXR 1.2
    • will add the feature proposal as a comment to the 4.9 wishlist on last week’s dev chat summary
  • @flixos90: thinking about ways to improve TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow
    • wondering whether it would be possible to automatically set a has-patch keyword once a 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. is uploaded?
    • It’s a bad experience for new contributors to search through tickets without a patch, but finding ones that already have one
    • will drop by #meta-tracdev to continue the conversation
  • @jnylen0: @enricosorcinelli working on #39732 and #39730
    • 39732 is a sanity improvement and a follow-up to work done around 4.7 in 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., should land soon for 4.9, but it would be good to get more eyes on it especially someone who has worked on comments before
    • 39730 may as well land at or around the same time as the above
  • @welcher: would love some eyes on Load word-count and do not allow our wp-utils script to clobber it

#4-8-1, #core, #dev-chat, #summary

Jeffrey Paul 5:40 pm on June 27, 2017
Tags: 4.8.1, , ,   

Dev Chat Agenda for June 28th (4.8.1 week 2)

This is the agenda for the weekly dev meeting on June 28, 2017 at 20:00 UTC:

  • 4.9 ideas
  • 4.8.1 planning
  • Editor, Customize, & REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. updates
  • Dev chat coordination (@jbpaul17)
  • New contributor 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. scrub/open office hours (@adamsilverstein)
  • General announcements

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!

#4-8-1, #agenda, #core, #dev-chat

Jeffrey Paul 4:24 am on June 23, 2017
Tags: 4.8.1, , ,   

Dev Chat Summary: June 21st (4.8.1 week 1)

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

4.9 ideas and brainstorm

  • No immediate 4.9 timeframe, but the planned timing for 4.9 will come shortly after we confirm the major focuses of 4.9 and will be closer to 3 months than 9 months in duration
  • @jorbin: Scheduled customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. changesets going live could be a big win
  • @westonruter: adding statuses for changesets: being able to draft a changeset to come back to later, and then to be able to schedule it to go live.
  • @youknowriad: We have some REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. needs in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/:
    • Retrieving The permalink using 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. (making more things available from wp-json/wp/v2/settings)
    • An API endpoint to save/get random settings (we’d use it to save some layout options)
  • @androb: Expanding link boundary behavior in TinyMCE to other inline elements
  • @androb: TinyMCE has a new mobile-optimized UXUX User experience that will also result in a responsive toolbar, this should land in the 4.9 time frame
  • @androd: tweak the TinyMCE UIUI User interface to be closer to Gutenberg (e.g. toolbar color, default font) to get users used to the Gutenberg UI before releasing that in WordPress 5.0
  • @saracannon: look at customizer revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. in a way that we might want to look at Gutenberg revisions in the future from a visual standpoint and start making progress there (@melchoyce: see mockup for customizer revisions on #21666)
  • @melchoyce: code editing improvements across coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. — CSSCSS Cascading Style Sheets. editing, the 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 code editor, etc. Making it better to use and harder to mess up and break your site (see #31779)
    • @clorith: As soon as we do this, we need to handle the issue of lacking forked plugins, lacking child theming etc
    • @westonruter: add a warning to encourage people to be aware of the dangers of editing code without version controlversion control A version control system keeps track of the source code and revisions to the source code. WordPress uses Subversion (SVN) for version control, with Git mirrors for most repositories. (see #41078)
  • @melchoyce: evisions for everything – Customizer revisions, page/post revisions, code editor revisions…
  • @hugobaeta: reduce the amount of declared colors (namely shades of gray) in the adminadmin (and super admin), more info on codepen and a little backstory on this flash talk at WCUS last year
  • @melchoyce: some in-progress tickets for improving theme switching: #39692, #39693
  • @melchoyce: also Customizer menu improvement – #40104
  • @melchoyce: automated testing in place for theme switching (@netweb to work on this)
  • @melchoyce: making “page on front” less confusing (again)
    • @westonruter: harmonizing with menus and page hierarchies. Merging those concepts together
  • @melchoyce: finish the gallery widget (@m1tk00 to work on this)

4.8.1 agenda

  • @westonruter: resolve text widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. removing code issue (see #40951) alongside implementing HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. code widget (see #40907), three options proposed, one recommended
  • a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) 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.-scrub will happen next Monday, will focus on 4.8.1 milestoned tickets
  • approaching 4.8.1 tickets as more traditional regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. types of issues
  • Tentative timeline for 4.8.1 last week of July

#4-8-1, #core, #dev-chat, #summary

Jeffrey Paul 7:27 pm on June 20, 2017
Tags: 4.8.1, , ,   

Dev Chat Agenda for June 21st (4.8.1 week 1)

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

  • 4.9 ideas and brainstorm
  • 4.8.1 agenda
  • Dev chat coordination
  • General announcements

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!

#4-8-1, #agenda, #core, #dev-chat