Call For Bugs

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.

At the start of the 4.3 cycle, I posted an open call for tickets that generated a list of 74 tickets including 25 bugs. All of the bugs reported have received some sort of comment since then, so it’s time to add onto the list. Starting with next week’s 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 we will use these bugs (along with the original list of 25) and continue to work on making sure they move forward.

If you have a bug that needs eyes on it, please comment with the ticketticket Created for both bug reports and feature development on the bug tracker.. In the immortal words of @wonderboymusic: “Help us help you.”

#4-3

welcher 8:06 pm on May 27, 2015

I’d love to have this re-visited https://core.trac.wordpress.org/ticket/31218.
- J.D. Grimes 8:17 pm on May 27, 2015
  
  That’s marked as an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature., not 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.. 🙂
  - welcher 8:23 pm on May 27, 2015
    
    Oops – disregard then 🙂
J.D. Grimes 8:15 pm on May 27, 2015

#16773
Rami Yushuvaev 8:18 pm on May 27, 2015

https://core.trac.wordpress.org/query?status=!closed&component=I18N&reporter=ramiy
- Rami Yushuvaev 8:22 pm on May 27, 2015
  
  All the tickets have patches. They are all from the same kind. Only one accepted so far (https://core.trac.wordpress.org/ticket/30614), 21 tickets left.
johnstonphilip 8:31 pm on May 27, 2015

Help me help you help me? https://core.trac.wordpress.org/ticket/30921
jeichorn 8:42 pm on May 27, 2015

https://core.trac.wordpress.org/ticket/31792
mrjarbenne 11:43 pm on May 27, 2015

I had mentioned this 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. in the initial call and I don’t see it amongst the 25. I think it falls nicely into the mobile UIUI User interface focus of 4.3 https://core.trac.wordpress.org/ticket/29606
Philip Arthur Moore 2:36 am on May 28, 2015

This was originally an Enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. that feels like a UXUX User experience 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. now: https://core.trac.wordpress.org/ticket/17470#comment:22.
Pascal Birchler 6:24 am on May 28, 2015

#17924
netomax 7:13 am on May 28, 2015

I’d like this https://core.trac.wordpress.org/ticket/32389 to be fixed, not a big thing but very helpful,
Spacedmonkey 8:55 am on May 28, 2015

This 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. is a real pain

https://core.trac.wordpress.org/ticket/31147
thomaswm 12:10 pm on May 28, 2015

This one is about rewrite rules for Multiste networks with subdirectories.
#20746
Ryan Boren 3:31 pm on May 28, 2015

https://core.trac.wordpress.org/query?status=!closed&keywords=~make-flow

I really want the four high priority tickets at the top of the list in 4.3.
programmin 7:20 pm on May 28, 2015

Please fix permalink bugs like this – just ran into this again today https://core.trac.wordpress.org/ticket/32048
David Anderson 11:13 pm on May 29, 2015

I haven’t been hit by this for a long time, but someone else (see the duplicate): https://core.trac.wordpress.org/ticket/26626 – has 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..

Comments are closed.

Welcome!

Communication

Share this: