Omnibox Bug Triage Process - Update Next Action Date for 2019

Bug: 
Change-Id: Iffcdf7971cd0842b470e4a215ff1be026d8f4c8f
Reviewed-on: https://chromium-review.googlesource.com/865832Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Justin Donnelly <jdonnelly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#530381}

components/omnibox/bug-triage.md

@@ -112,7 +112,7 @@ Follow [standard Chromium
 policies](https://www.chromium.org/for-testers/bug-reporting-guidelines/triage-best-practices).
 *Priority-2* represents wanted for this release but can be punted for a release.
 *Priority-3* are bugs not time sensitive.  There is an even-lower-priority
-state; see the *NextAction=01/09/2018* below.
+state; see the *NextAction=01/08/2019* below.
 
 ### Owners
 
@@ -164,7 +164,7 @@ The subcomponents of omnibox bugs include:
 | UI>Browser>Omnibox>ZeroSuggest | Suggestions displayed on omnibox focus (both contextual and non-contextual). |
 
 If the bug is extremely low priority, set the **NextAction field** to
-**01/09/2018** and mention that we will "reassess" the bug next year.  This
+**01/08/2019** and mention that we will "reassess" the bug next year.  This
 NextAction field is for Priority-3 bugs that are somehow less important than
 other *priority-3* bugs.  These are bugs we’re sure no one on the team intends
 to fix this year (e.g., really unimportant, or mostly unimportant and hard to