The Crashpad issue tracker is migrating to the Chromium tracker today
10 views
Skip to first unread message
Mark Mentovai
Jun 20, 2024, 11:29:28 AMJun 20
to Crashpad-dev
Hi!
As you may be aware, Chromium moved over to a new issue tracker earlier this year. Crashpad will follow and migrate as subcomponents within the top-level Chromium component.
The migration is on track to begin today at 16:30Z = 12:30pm Eastern = 09:30am Pacific, and we expect that the migration will be completed by the end of the day. There will be downtime during this period as the Crashpad issue tracker within Monorail will be marked as read-only. The new Crashpad component within the Chromium issue tracker will not be available until the migration is completed.
Mark
As you may be aware, Chromium moved over to a new issue tracker earlier this year. Crashpad will follow and migrate as subcomponents within the top-level Chromium component.
The migration is on track to begin today at 16:30Z = 12:30pm Eastern = 09:30am Pacific, and we expect that the migration will be completed by the end of the day. There will be downtime during this period as the Crashpad issue tracker within Monorail will be marked as read-only. The new Crashpad component within the Chromium issue tracker will not be available until the migration is completed.
Mark
Mark Mentovai
Jun 20, 2024, 3:55:10 PMJun 20
to Crashpad-dev
Hi again!
The Crashpad issue tracker migration to Buganizer is now complete!
Old bug links will redirect to the new bug tracker, with new numbers.
Please use the newly created Crashpad component within the top level Chromium component to search for and file bugs.
Please use the newly created Crashpad component within the top level Chromium component to search for and file bugs.
With a special thanks to the team that worked on this migration up to and including today,
Mark
Reply all
Reply to author
Forward
0 new messages