-
-
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
Deprecations: list of all past and ongoing deprecations #10587
Labels
Comments
humitos
added
Improvement
Minor improvement to code
Accepted
Accepted issue on our roadmap
labels
Aug 1, 2023
humitos
added a commit
that referenced
this issue
Aug 1, 2023
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
This looks good. I might align the Sphinx 1.8 & Mkdocs .17 dates, since they seem like basically the same deprecation (eg. removing old default build tools). |
humitos
added a commit
that referenced
this issue
Aug 3, 2023
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
1 task
humitos
added a commit
that referenced
this issue
Aug 9, 2023
…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 <aj@ohess.org> Co-authored-by: Eric Holscher <25510+ericholscher@users.noreply.github.com> * 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 <aj@ohess.org> Co-authored-by: Eric Holscher <25510+ericholscher@users.noreply.github.com>
humitos
added a commit
that referenced
this issue
Aug 9, 2023
* 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 <aj@ohess.org> Co-authored-by: Eric Holscher <25510+ericholscher@users.noreply.github.com> * 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 * Deprecation: codify browndates for "no config file deprecation" Follows https://github.com/readthedocs/blog/pull/233/files#r1283479184 This way, we don't have to enable anything manually. These dates are already communicated to users and will be automatically applied. --------- Co-authored-by: Anthony <aj@ohess.org> Co-authored-by: Eric Holscher <25510+ericholscher@users.noreply.github.com>
2 tasks
We are deprecating webhooks created without a secret on January 31st, 2024. https://blog.readthedocs.com/security-update-on-incoming-webhooks/ |
6 tasks
Looks like #9530 has taken affect (status not updated here)? Just noticed traffic fell off a cliff recently. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We have been deprecating pretty old non-used or broken features in the last weeks and we found ourselves a little lost about the big picture (whole plan) but also about what are the features that are going through the deprecation time. This issue just list them all here with the exact dates when they are making effective:
#10514: Drop PyPy support#10550: Fail builds withoutindex.html
#10508: Install latest version of requirements#10494: RemoveUPDATE_CONDA_STARTUP
#10588: RemoveDONT_SHALLOW_CLONE
#5609: Doctools without config file#10562: Removepython.system_packages
#10367: No.readthedocs.yaml
and v1#10584: Drop support for MkDocs 0.17.3#10365: Drop support for Sphinx 1.x#10589: Dropbuild.image
#8840: Drop VCS (svn
,hg
,bzr
)#11206: DropMKDOCS_THEME_RTD
feature flag#9993: Don't serveREADME.html
at /#11441: Don't auto-inject Sphinx context/configs#9530: Auto-injection of Google Analyticssetup.py install
conf.py
andmkdocs.yml
Related: #9779
The text was updated successfully, but these errors were encountered: