-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
VCS: deprecation dates at application level #11147
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Follow the dates published in our blog: https://about.readthedocs.com/blog/2024/02/drop-support-for-subversion-mercurial-bazaar/ Closes #8840
ericholscher
approved these changes
Feb 26, 2024
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.
We should socialize this blog post a bit more. I think newsletter & social is a good spot to start, but we should also email all the effected users again with an update.
Co-authored-by: Eric Holscher <[email protected]>
…hedocs.org into humitos/vcs-deprecated
…mitos/vcs-deprecated
humitos
added a commit
that referenced
this pull request
Jun 4, 2024
This PR removes the code for old VCS support. Besides, it touches the documentation slightly to remove mentions to particular VCS (Mercurial, Bazaar, SVN). However, it doesn't re-write all parts of the documentation where we are using "VCS" in a generic way. There should be another PR that re-phrase those senteces to mention Git directly. Related: * #11147 * #8840 * https://about.readthedocs.com/blog/2024/02/drop-support-for-subversion-mercurial-bazaar/
humitos
added a commit
that referenced
this pull request
Jun 10, 2024
* VCS: remove code for old VCS support This PR removes the code for old VCS support. Besides, it touches the documentation slightly to remove mentions to particular VCS (Mercurial, Bazaar, SVN). However, it doesn't re-write all parts of the documentation where we are using "VCS" in a generic way. There should be another PR that re-phrase those senteces to mention Git directly. Related: * #11147 * #8840 * https://about.readthedocs.com/blog/2024/02/drop-support-for-subversion-mercurial-bazaar/ * Add migrations * Update readthedocs/projects/constants.py Co-authored-by: Eric Holscher <[email protected]> --------- Co-authored-by: Eric Holscher <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow the dates published in our blog:
https://about.readthedocs.com/blog/2024/02/drop-support-for-subversion-mercurial-bazaar/
Closes #8840