Context Navigation

Changes between Initial Version and Version 1 of Ticket #50992, comment 31

-                      initial
+                      v1
 Now I need to change the workflow again. I can't use a database because the first check happens before WP is loaded, I'll probably revert back to my own environment management.
 My point is that when support for a constant is added, it should not be removed in a** bugfix release** that, as you know, might happen to be pushed overnight on environments via automatic updates.
+My point is that when support for a constant is added, it should not be removed in a **point release** that, as you know, might happen to be pushed overnight on environments via automatic updates.
 I see you added a deprecation notice if WP_ENVIRONMENT_TYPES is defined, why not _just_ keep this notice and wait at list next minor to remove support?
+I see you added a deprecation notice if WP_ENVIRONMENT_TYPES is defined, why not ''just'' keep this notice and wait at list next major to remove support?
 Is not that the point of deprecation notices? First you deprecate, in next version you remove. Or am I wrong?
+Is not that the point of deprecation notices? First, you deprecate, in the next version you remove. Or am I wrong?
 But I guess is too late now.
+But I guess it's too late now.