Context Navigation

Changes between Initial Version and Version 1 of Ticket #6783, comment 6

initial	v1
6	6	> I'm not 100% familiar with how the `task` label is used today, but looking at the [https://core.trac.wordpress.org/query?status=!closed&type=task+(blessed) list of open tasks on core.trac] and [https://meta.trac.wordpress.org/query?status=!closed&type=task+(blessed) meta.trac] the majority seem to be enhancements/bugs/todo-list items, but then there's some like `Prepare for PHP 8.2` which are both enhancements and bugs at the same time, but something that just needs to happen, and thus, is a task.
7	7
8		Currently the `task` ticket type is used for two different things:
	8	Yep, currently the `task` ticket type is used for two different things:
9	9	- For tickets that are "tasks", not bugs and not enhancements, or a bit of both. `Prepare for PHP 8.2` is a good example. These tasks usually run for longer time and are not milestone dependent.
10	10	- To extend the feature freeze deadline for specific enhancement past beta 1. This relies on the "not milestone dependent" status of tasks and used to be a rare exception. Recently many enhancements coming from Gutenberg are marked as tasks just before beta 1. This doesn't seem as the "proper" use of this ticket type. Hopefully this will change soon (made a proposal to change it: https://make.wordpress.org/core/2023/02/18/proposal-updates-to-the-wordpress-release-cycle/).