-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecation: notification and feature flag for build.image
config
#10589
Conversation
Define a weekly task to communicate our users about the deprecation of `build.image` using the deprecation plan we used for the configuration file v2 as well. - 3 brownout days - final removal date on October 2nd - weekly onsite/email notification on Wednesday at 11:15 CEST (around 3.5k projects affected) - allow to opt-out from these emails - feature flag for brownout days - build detail's page notification Related: * readthedocs/meta#48 * #10354 * #10587
Define a weekly task to communicate our users about the deprecation of `build.image` using the deprecation plan we used for the configuration file v2 as well. - 3 brownout days - final removal date on October 2nd - weekly onsite/email notification on Wednesday at 11:15 CEST (around ~22k projects affected) - allow to opt-out from these emails - feature flag for brownout days - build detail's page notification Related: * readthedocs/meta#48 * #10354 * #10587
…:readthedocs/readthedocs.org into humitos/deprecate-build-image-config-key
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, and similar to our other approach. A few questions, but I think it's close.
readthedocs/templates/projects/notifications/deprecated_build_image_used_email.txt
Outdated
Show resolved
Hide resolved
readthedocs/templates/projects/notifications/deprecated_build_image_used_email.txt
Show resolved
Hide resolved
readthedocs/templates/projects/notifications/deprecated_build_image_used_email.txt
Outdated
Show resolved
Hide resolved
Co-authored-by: Anthony <[email protected]> Co-authored-by: Eric Holscher <[email protected]>
I applied all the suggestions. I will update the HTML email and we will be ready to approve and merge, I guess. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I'm fine emailing more folks at first, then dropping it down, we should just make sure the email content matches the actual timeframe used 👍
* Post: Use `build.os` instead of `build.image` Announcement for readthedocs/readthedocs.org#10589 * Apply suggestions from code review Co-authored-by: Eric Holscher <[email protected]> * Update date --------- Co-authored-by: Eric Holscher <[email protected]>
We will start with 3 years timeframe first and then lower it down to 1 year.
Define a weekly task to communicate our users about the deprecation of
build.image
(or not specifyingbuild.os
) using the deprecation plan we used for the configuration file v2 as well.Related:
Closes: