In software and product development, tasks are often categorized by priority levels (P0, P1, P2, P3, P4). These levels help teams distinguish between critical emergencies and long-term enhancements, ensuring that urgent issues are resolved quickly while less impactful tasks are scheduled appropriately.

Currently, WordPress Developer Docs do not provide a clear explanation of these priority levels. Adding this documentation will help contributors, plugin developers, and core maintainers align on urgency and impact when triaging issues or planning releases.

Proposed Content Outline

1. Introduction

   • What priority levels mean in software development
   • Why WordPress contributors should adopt a shared understanding

2. Priority Levels Explained

   • P0 (Critical): System outage, site-breaking bugs, immediate all-hands response
   • P1 (High): Major feature malfunction, urgent but within normal schedule
   • P2 (Moderate): Minor feature malfunction, important but can be prioritized against other issues
   • P3 (Low): Small functionality issues affecting limited users, part of routine work
   • P4 (Negligible): Wishlist items or minor enhancements, backlog candidates

3. Examples in WordPress Context

   • P0: WordPress core update causes fatal errors on all sites
   • P1: Gutenberg editor fails to load for most users
   • P2: Specific block misalignment in certain themes
   • P3: Minor accessibility improvement for a niche use case
   • P4: Experimental feature idea for future releases

4. Best Practices

   • How to triage issues using P-levels
   • Avoiding “everything is P0” syndrome
   • Encouraging contributors to document priority when submitting issues

Benefits

• Provides clarity for contributors and developers
• Improves triage efficiency in WordPress core and plugin development
• Aligns WordPress with broader software development practices