Yesterday, the new weekly contributor meeting was held in the #core Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. room. Here is a recap of the meeting. A full chat log is also available.
Participants: @adamsilverstein @asalce @azerial @chetan200891 @circlecube @clorith @desrosj @dipeshkakadiya @dnavarrojr @e_baker @helen @jdmensing @johnbillion @jorbin @josiahsprague @joyously @kelseyfecho @linsoftware @luckyankit @milindmore22 @mte90 @nabil_kadimi @proscriptsell @punit5658 @stevenkword @t-rave @welcher @zakkath
Before Creating Tickets
- Before creating a ticket Created for both bug reports and feature development on the bug tracker., there are a few things you should do:
- Ensure you are running the latest version of WordPress (if reporting a bug 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.).
- Search Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to make sure a ticket for your bug or enhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature..
- Creating a duplicate ticket is ok, as long as you did your best to find a pre-existing ticket.
Writing a Title
- A good ticket title should accurately summarize the problem the ticket addresses.
- Someone should be able to see the title and get the general idea of what the ticket is trying to solve, not the solution.
Writing a Description
- A ticket description should include:
- A description of the behavior you expect and why
- A description of the behavior you are seeing
- Steps to reproduce the behavior so other contributors can see it for themselves and track down the source.
- If an enhancement ticket, describe what it improves upon and why this is beneficial.
- If it involves something else (like a specific browser, or server type), make sure to detail that as well.
- If applicable, screenshots are also very helpful.
- Screenshots are best uploaded directly to Trac. This prevents images from becoming dead links when removed from external image sources.
- Always try to focus on the problems being solved, even if it’s an enhancement, you are trying to solve a problem of some sort.
Examples of tickets with good titles and descriptions: #41525, #37013.
What is the difference between Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and Meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Trac?
Core Trac is meant for tickets relating to the WordPress software you install and run (including unit tests). Meta Trac is meant for a bunch of other things, but mainly things that are WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ related. There is a full list at the top of the Meta Trac home page.
It is very important that any issues with security implications be reported through responsible disclosure privately. For more information on reporting security vulnerabilities, see the WordPress Handbook.
What is considered “enough testing”?
- This will vary based on the ticket and what problem is being solved.
- Testing may span multiple releases for complex problems.
- It also is up to the committer A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. that chooses to take ownership of the ticket. They need to be completely comfortable with the change, and confident that there is little to no potential for issues.
- Once committed, the testing does not end. Testing continues by using
- After that, the alpha, beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process., and RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). releases are in place to catch anything that might have been missed.
Is there a protocol for old tickets that have become stagnant?
- Check that the problem or enhancement in the ticket is still relevant.
- Test any patches on the ticket to ensure they still apply cleanly.
- Test that the patch 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. still solves the issue.
- Add the
needs-refresh tag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) if not.
- Stagnant tickets can be frustrating, but remember, no one is purposefully ignoring your efforts. Most (if not all) of the folks here are volunteers working in their free time.
- #39535 – Canonical redirects disallow tag named comments
- #37057 – Creation of an esc_html functions for _n(), _nx(), _ex(), and number_format_i18n()
- #41521 – Menu list with dropdown icon alignment bug in responsive.
- #41497 – Menu has style problem in listing on admin (and super admin) menu page
Next Week’s Meeting
The next meeting will take place in the #core slack channel on Wednesday, August 9, 19:00 UTC. Please feel free to drop in with any questions or tickets you’d like to discuss!
Thanks to everyone that attended! As always, please feel free to leave a comment below or reach out to any of the moderators (@adamsilverstein, @desrosj, @stevenkword, @welcher) with questions on Slack.