Monorail Onboarding for libyuv

[Aaron Gable]

Welcome aboard!

Hopefully you are aware that code.google.com is shutting down imminently, and this includes the issue tracker.  Chrome’s infrastructure team has been hard at work on a replacement, Monorail[1], and we are ready for your project to come aboard.

We plan to migrate libyuv, on Wednesday, March 16, at 4pm Pacific (23:00 UTC).

What you can expect:

• Your full project has been copied to our staging server for you to peruse first.  See your project at https://monorail-staging.appspot.com/p/libyuv/issues/list.  Let us know if you see any problems. (Note: this is a copy of your issues as of a day or so ago, it is not continually updated from code.google.com).
  
• Very minimal disruption during migration. Your code.google.com project will be marked read-only before the migration. Expected total downtime is less than one hour.
  
• Full fidelity import of your all existing issues from https://code.google.com/p/libyuv/issues/list
  
• Support from our team
  
• File issues against Monorail itself at https://monorail-prod.appspot.com/p/monorail/issues/list
• Contact us at infra-dev...@chromium.org

If you use the code.google.com API in any way, please get in touch with us and we will whitelist you to use the new Monorail API, and get you started using the new system. You can see more details in the "Changes You May Have To Make" section of our FAQ here.

Thanks,

Aaron, on behalf of the Monorail team

[1] https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/fzSq2mipdmU

P.S. Apologies if you have received this message already; sending from an address which can successfully post to discuss-libyuv@.

[Frank Barchard]

looks good.  cant modify of course.  i update issues almost daily, so getting write access would be good.  otherwise i need to keep updating the old one

will it be hooked up so that landing a change will update the issue?

will it be hooked into code reviews, so referring to an issue # in the BUG= field will refer to libyuv issues?

On Mon, Mar 14, 2016 at 2:37 PM, Aaron Gable <aga...@chromium.org> wrote:

Welcome aboard!

Hopefully you are aware that code.google.com is shutting down imminently, and this includes the issue tracker.  Chrome’s infrastructure team has been hard at work on a replacement, Monorail[1], and we are ready for your project to come aboard.

We plan to migrate libyuv, on Wednesday, March 16, at 4pm Pacific (23:00 UTC).

What you can expect:

• Your full project has been copied to our staging server for you to peruse first.  See your project at https://monorail-staging.appspot.com/p/libyuv/issues/list.  Let us know if you see any problems. (Note: this is a copy of your issues as of a day or so ago, it is not continually updated from code.google.com).
  
• Very minimal disruption during migration. Your code.google.com project will be marked read-only before the migration. Expected total downtime is less than one hour.
  
• Full fidelity import of your all existing issues from https://code.google.com/p/libyuv/issues/list
  
• Support from our team
  

• File issues against Monorail itself at https://monorail-prod.appspot.com/p/monorail/issues/list

• Contact us at infra-dev+monorail@chromium.org

If you use the code.google.com API in any way, please get in touch with us and we will whitelist you to use the new Monorail API, and get you started using the new system. You can see more details in the "Changes You May Have To Make" section of our FAQ here.

Thanks,

Aaron, on behalf of the Monorail team

[1] https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/fzSq2mipdmU

P.S. Apologies if you have received this message already; sending from an address which can successfully post to discuss-libyuv@.

--
You received this message because you are subscribed to the Google Groups "discuss-libyuv" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-libyuv+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aaron Gable]

Reminder: this is scheduled to begin in half an hour from now. I will be updating my tracking bug and this thread as the migration progresses. I expect it to take less than an hour.

Thanks,

Aaron

[Aaron Gable]

This is starting now. You can expect code.google.com/p/libyuv to go read-only momentarily.

[Aaron Gable]

This is now complete! You can see the new tracker at bugs.chromium.org/p/libyuv, and all links to the old tracker will automatically redirect to the corresponding page on Monorail.

If you have any questions or issues, please reach out to us at infra-dev...@chromium.org, or file a bug against us at bugs.chromium.org/p/monorail.

Thanks!

Please keep your hands and feet inside the ride at all times!