Chromium moving to a different issue tracker

[Rick Byers]

Hi all,

We wanted to share that Chromium is moving to a different Issue Tracker to provide a well-supported user experience for the long term. This will occur no earlier than 2024 -- please see below for details!

What’s happening

Chrome will be migrating all Chromium issues, including issue history, from Monorail to a different tool: Chromium Issue Tracker. On behalf of the Chromium community, Google explored different tooling options, as Monorail will no longer be maintained. This tooling change is an effort to provide a feature-rich and well supported issue tracker for Chrome ecosystem open source projects. With this migration, Chrome is moving to a fully-supported issue tracker with regular feature improvements being deployed. Existing transparency levels will be maintained. This means that existing access to and public disclosure of security issues will be maintained in the migration.

Timing

Chromium will migrate no earlier than 2024 (timeline details will be shared once finalized later in the year). 

Migration Readiness

In due course, we will share additional resources, including a walkthrough of the new issue tracker, highlighting key features. There will be no tooling changes until the readiness criteria are met.

Post-Migration 

While there will be differences, we are working to make the migration straightforward. Once the migration completes, existing Monorail issue links will redirect to the migrated issues in the new issue tracker. 

Help & Feedback

If you have any questions or anticipate complications due to this migration, please reach out to issue-trac...@chromium.org, so the migration team can help ensure an easy transition.

[PhistucK]

A little sad!

Mildly related - will the new tracker also be open source? Does it already exist (anything to show?) publicly, in testing?

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium Embedders" group.
To unsubscribe from this group and stop receiving emails from it, send an email to embedder-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/embedder-dev/CAFUtAY-bmgyL1AoObcVTAp7Nf2or-UxT6sDXTTn7dgNq7Awqdg%40mail.gmail.com.

[Rick Byers]

Hi all,

PhistucK and I discussed a bit privately, but I wanted to answer publicly as well after some internal coordination.

The new issue tracker will be a variation of Google's issue tracker, which isn't open source. We're significantly investing in the tracker to better support open source projects like Chromium. You can see it in use now for the Gerrit project at https://issues.gerritcodereview.com/issues, which recently migrated from Monorail. We'll be adding more features, and configuring it differently for Chromium to ensure it meets the needs of our large and diverse open source community. So it won't be exactly what you see for Gerrit. I'm sure there's going to be some growing pains as we move over to it, but ultimately I'm confident it's going to be an upgrade.

Thanks,

   Rick

[Adrià Vilanova Martínez]

Hey,

It's indeed sad to see that Monorail will no longer be maintained. 😢 I'm personally hosting an instance to track my security research and some personal projects.

Maybe it would be nice to post an announcement about the future plans of Monorail at infra-dev@.[1] That way other folks who might be running a Monorail instance also get to know about this. And if that was the case, the community could try to come together and continue maintaining it (similarly to what happened with Phabricator). Not that I'd personally want to use Monorail instead of Buganizer, but the latter is out of reach ;)

Have a nice weekend!

PS: Sorry if this was off-topic. This is the only place where I read that Monorail will no longer be maintained.

[1]: Monorail Issue Tracker User Guide – How to ask for help and report problems with Monorail itself

[Rick Byers]

This migration is now in progress with monorail now read-only and the new system expected to come online by start-of-day Monday. Any time-critical issues over the weekend can be raised via e-mail as described here. Please have patience next week while we all get used to the new system and iron out any urgent issues. I've also created an #issue-tracker channel in the Chromium slack for sharing tips and tricks and general discussion on the new system.

Cheers,

   Rick