You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deprecation: notification and feature flag for build.image config (#10589)
* Deprecation: notification and feature flag for `build.image` config
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
* Deprecation: notification and feature flag for `build.image` config
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
* Review and update logic
* Start emailing people with projects building from 3 years ago
* Apply suggestions from code review
Co-authored-by: Anthony <[email protected]>
Co-authored-by: Eric Holscher <[email protected]>
* Add HTML version of the email
* Codify brownout dates and remove the feature flag
Follows the suggestion from https://github.com/readthedocs/blog/pull/233/files#r1283479184
* Use UTC datetimes to compare
* Contact projects with a build in the last 3 years
We will start with 3 years timeframe first and then lower it down to 1 year.
---------
Co-authored-by: Anthony <[email protected]>
Co-authored-by: Eric Holscher <[email protected]>
The <code>build.image</code> config key on <code>.readthedocs.yaml</code> has been deprecated, and will be removed on <strong>October 16, 2023</strong>.
4
+
We are sending weekly notifications about this issue to all impacted users,
5
+
as well as temporary build failures (brownouts) as the date approaches for those who haven't migrated their projects.
6
+
7
+
The timeline for this deprecation is as follows:
8
+
9
+
<ul>
10
+
<li><strong>Monday, August 28, 2023</strong>: Do the first brownout (temporarily enforce this deprecation) for 12 hours: 00:01 PST to 11:59 PST (noon)</li>
11
+
<li><strong> Monday, September 18, 2023</strong>: Do a second brownout (temporarily enforce this deprecation) for 24 hours: 00:01 PST to 23:59 PST (midnight)</li>
12
+
<li><strong> Monday, October 2, 2023</strong>: Do a third and final brownout (temporarily enforce this deprecation) for 48 hours: 00:01 PST to October 3, 2023 23:59 PST (midnight)</li>
13
+
<li><strong> Monday, October 16, 2023</strong>: Fully remove support for building documentation using "build.image" on the configuration file</li>
14
+
</ul>
15
+
16
+
We have identified that the following projects which you maintain, and were built in the last year, are impacted by this deprecation:
<li>... and {{ projects.count|add:"-15" }} more projects.</li>
24
+
{% endif %}
25
+
</ul>
26
+
27
+
Please use <code>build.os</code> on your configuration file to ensure that they continue building successfully and to stop receiving these notifications.
28
+
If you want to opt-out from these emails, you can <ahref="https://readthedocs.org/accounts/edit/"> edit your preferences in your account settings</a>.
29
+
30
+
For more information on how to use <code>build.os</code>,
31
+
<ahref="https://blog.readthedocs.com/use-build-os-config/">read our blog post</a>
32
+
33
+
Get in touch with us <ahref="{{ production_uri }}{% url 'support' %}">via our support</a>
34
+
and let us know if you are unable to use a configuration file for any reason.
0 commit comments