Upcoming Gerrit issue tracker changes

[Edwin Kempin]

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

We will migrate all Gerrit issues, including issue history, into the new Gerrit Code Review Tracker. When the migration starts, the Gerrit project in Monorail will be placed into read-only mode. We anticipate the migration will take ~3-4 hours.

With this migration, we are moving to a fully-supported issue tracker with regular feature improvements being deployed. Additionally, we anticipate an improvement in the responsiveness of the Gerrit team at Google, by eliminating dual tracker pains. 

You can learn more about the new issue tracker's features at: developers.google.com/issue-tracker. 

The new issue tracker will be available at: issues.gerritcodereview.com. (Please note that it is not yet available there, and you will get a 404 error if you try to access it now). We will send a further email once migration has completed. 

Thank you!

Edwin on behalf of the Gerrit Code Review Team

[James Muir]

On Wed, May 17, 2023 at 5:13 AM 'Edwin Kempin' via Repo and Gerrit Discussion <repo-d...@googlegroups.com> wrote:

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

We will migrate all Gerrit issues, including issue history, into the new Gerrit Code Review Tracker. When the migration starts, the Gerrit project in Monorail will be placed into read-only mode. We anticipate the migration will take ~3-4 hours.

With this migration, we are moving to a fully-supported issue tracker with regular feature improvements being deployed. Additionally, we anticipate an improvement in the responsiveness of the Gerrit team at Google, by eliminating dual tracker pains. 

Can you explain what you mean by "dual tracker pains"?

The info at https://www.gerritcodereview.com/issues.html points people to bugs.chromium.org only.  Is there some other internal issuer tracker google employees see?

I have only filed one issue at bugs.chromium.org, but it has been a year and it still has not been triaged :-)  There appear to be quite a large number of issues that haven't been triaged.  If this migration can improve responsiveness, then I think it is worth doing.

-James M

[David Ostrovsky]

James Muir schrieb am Samstag, 20. Mai 2023 um 22:00:25 UTC+2:

On Wed, May 17, 2023 at 5:13 AM 'Edwin Kempin' via Repo and Gerrit Discussion <repo-d...@googlegroups.com> wrote:

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

We will migrate all Gerrit issues, including issue history, into the new Gerrit Code Review Tracker. When the migration starts, the Gerrit project in Monorail will be placed into read-only mode. We anticipate the migration will take ~3-4 hours.

With this migration, we are moving to a fully-supported issue tracker with regular feature improvements being deployed. Additionally, we anticipate an improvement in the responsiveness of the Gerrit team at Google, by eliminating dual tracker pains. 

Can you explain what you mean by "dual tracker pains"?

See this announcement for using internal Google issue tracker in Gerrit project

for more context: [1].

Basically, with the new move from Monorail to internal Google issue tracker

this disadvantage:

"We understand that this is not ideal, because non-Googlers cannot open these links."

could be resolved per issue, if Googler mark internally filed issue as publicly visible.

[1] https://groups.google.com/g/repo-discuss/c/0IaEygcdyNI/m/Q_LSe_MNCAAJ

[Edwin Kempin]

On Sat, May 20, 2023 at 10:00 PM James Muir <jm...@crypto4a.com> wrote:

On Wed, May 17, 2023 at 5:13 AM 'Edwin Kempin' via Repo and Gerrit Discussion <repo-d...@googlegroups.com> wrote:

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

We will migrate all Gerrit issues, including issue history, into the new Gerrit Code Review Tracker. When the migration starts, the Gerrit project in Monorail will be placed into read-only mode. We anticipate the migration will take ~3-4 hours.

With this migration, we are moving to a fully-supported issue tracker with regular feature improvements being deployed. Additionally, we anticipate an improvement in the responsiveness of the Gerrit team at Google, by eliminating dual tracker pains. 

Can you explain what you mean by "dual tracker pains"?

The info at https://www.gerritcodereview.com/issues.html points people to bugs.chromium.org only.  Is there some other internal issuer tracker google employees see?

Yes, exactly. The Gerrit team at Google uses an internal issue tracker to track their work. This is also where most of the issues from Googlers are filed.

At the moment these issues cannot easily be shared with the community, as moving issues between the issue trackers is not supported. 

With the migration we will basically move to the same issue tracker that we use internally, so that moving issues between public and internal components will be possible.

 

I have only filed one issue at bugs.chromium.org, but it has been a year and it still has not been triaged :-)  There appear to be quite a large number of issues that haven't been triaged.  If this migration can improve responsiveness, then I think it is worth doing.

Yes, we are aware that issue triaging is one of our weak spots.

As an open source project we can't offer any guaranteed response times nor SLOs [1], but we largely depend on the community to help out with this.

As Google we do triage Monorail issues that affect our servers [2], but they currently are less visible than our internal issues. With the migration this will improve, as it will allow us to see all issues that concern us in a single dashboard.

[1] https://www.gerritcodereview.com/support.html#response-time-and-slo

[2] https://www.gerritcodereview.com/support.html#google

 

-James M

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/CAM-GoEWjH_h0y32P1fCLVu5WxY8WuUF7E1DvKPcrTGD9f%2BcUyw%40mail.gmail.com.

[Edwin Kempin]

On Wed, May 17, 2023 at 11:13 AM Edwin Kempin <eke...@google.com> wrote:

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

The migration is now scheduled for June 14th 2023.

We will start at 9:00AM PT / 6:00PM CEST and expect the migration to be finished at 13:30AM PT / 10:30PM CEST.

During the migration Gerrit issues are read-only. In urgent cases please report issues via the mailing list or on Discord.

[Edwin Kempin]

On Friday, June 9, 2023 at 12:32:13 PM UTC+2 Edwin Kempin wrote:

On Wed, May 17, 2023 at 11:13 AM Edwin Kempin <eke...@google.com> wrote:

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

The migration is now scheduled for June 14th 2023.

We will start at 9:00AM PT / 6:00PM CEST and expect the migration to be finished at 13:30AM PT / 10:30PM CEST.

During the migration Gerrit issues are read-only. In urgent cases please report issues via the mailing list or on Discord.

Heads up, we will do the migration today as planned, see this announcement.

[Edwin Kempin]

On Wednesday, June 14, 2023 at 5:38:33 PM UTC+2 Edwin Kempin wrote:

On Friday, June 9, 2023 at 12:32:13 PM UTC+2 Edwin Kempin wrote:

On Wed, May 17, 2023 at 11:13 AM Edwin Kempin <eke...@google.com> wrote:

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

The migration is now scheduled for June 14th 2023.

We will start at 9:00AM PT / 6:00PM CEST and expect the migration to be finished at 13:30AM PT / 10:30PM CEST.

During the migration Gerrit issues are read-only. In urgent cases please report issues via the mailing list or on Discord.

Heads up, we will do the migration today as planned, see this announcement.

The migration is successfully done now, please see this announcement.

[pon...@gmail.com]

Hi Edwin,

On Wednesday, 14 June 2023 at 22:44:12 UTC+2 Edwin Kempin wrote:

On Wednesday, June 14, 2023 at 5:38:33 PM UTC+2 Edwin Kempin wrote:

On Friday, June 9, 2023 at 12:32:13 PM UTC+2 Edwin Kempin wrote:

On Wed, May 17, 2023 at 11:13 AM Edwin Kempin <eke...@google.com> wrote:

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

The migration is now scheduled for June 14th 2023.

We will start at 9:00AM PT / 6:00PM CEST and expect the migration to be finished at 13:30AM PT / 10:30PM CEST.

During the migration Gerrit issues are read-only. In urgent cases please report issues via the mailing list or on Discord.

Heads up, we will do the migration today as planned, see this announcement.

The migration is successfully done now, please see this announcement.

 

Thanks for taking care of the migration.

When creating an issue, I noticed we don't have the "bug template" as in the previous issue tracker.

Are you planning to add it to the new issue tracker or not necessarily?

[pon...@gmail.com]

On Friday, 16 June 2023 at 12:13:41 UTC+2 pon...@gmail.com wrote:

Hi Edwin,

On Wednesday, 14 June 2023 at 22:44:12 UTC+2 Edwin Kempin wrote:

On Wednesday, June 14, 2023 at 5:38:33 PM UTC+2 Edwin Kempin wrote:

On Friday, June 9, 2023 at 12:32:13 PM UTC+2 Edwin Kempin wrote:

On Wed, May 17, 2023 at 11:13 AM Edwin Kempin <eke...@google.com> wrote:

Hi everyone,

We want to let you know that we are getting ready to make changes to the way Gerrit issues are tracked, aiming for cutover by early June 2023 (subject to change). 

The migration is now scheduled for June 14th 2023.

We will start at 9:00AM PT / 6:00PM CEST and expect the migration to be finished at 13:30AM PT / 10:30PM CEST.

During the migration Gerrit issues are read-only. In urgent cases please report issues via the mailing list or on Discord.

Heads up, we will do the migration today as planned, see this announcement.

The migration is successfully done now, please see this announcement.

 

Thanks for taking care of the migration.

When creating an issue, I noticed we don't have the "bug template" as in the previous issue tracker.

Are you planning to add it to the new issue tracker or not necessarily?

Ops...scratch it! The template is already in place :)

Discard my previous post.