-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Conversation
… 2.0 URLs from whats-new.yml
…tml, Replace {{ site.baseurl}}guides/v2.0/ , replaced MRG/BIC links
…will work as expected
@jeff-matthews, XLSX is a format that requires a proprietary software to open it. Could you please replace it with CSV or ODS if possible? |
GitHub doesn't accept CSV or ODS formats. |
Good to know |
guides/v2.1/architecture/archi_perspectives/components/modules/mod_and_areas.md
Outdated
Show resolved
Hide resolved
I reverted the commit that globally replaced 2.0 redirects in file metadata (4361cac). I'm going to proceed with the new plan to remove all 2.0 redirects in file metadata. |
Ok, I removed all 2.0 redirects from the file metadata and updated the S3 config on staging. If a 2.3 file exists for an incoming 2.0 URL, S3 will redirect to that page. For example:
If a 2.3 file does not exist for an incoming 2.0 URL, S3 will redirect to the home page of the latest version of devdocs (currently 2.3). For example:
Incidentally, this config eliminates the possibility of getting a 404 on 2.3 pages. |
Thanks for the review and improvements @dobooth. Does anyone else want to offer an opinion on this before I put it in motion? |
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.
No need to exclude guides/v2.0
in the configuration, because when we remove the corresponding declaration in the Docfile, the directory will not even exist as a part of the project during its build.
Should the corresponding update of the Docfile and rake tasks be a part of this PR?
Good point @dshevtsov. I'll make the update. |
… from Docfile.yml
…docs into MAGEDOC-3469-remove-EOL-docs
running tests |
Tests failed
|
…docs into MAGEDOC-3469-remove-EOL-docs
running tests |
Hi @jeff-matthews, thank you for your contribution! |
Purpose of this pull request
This pull request (PR) removes all
guides/v2.0
content from the devdocs site since 2.0 has reached end-of-life (EOL) and no longer receives security patches, quality fixes, or documentation updates.This PR also replaces
v2.0
in redirect metadata withv2.3
so that S3 can route URLs to the right file since we're configuring S3 to replacev2.0
in ALL inbound URLS withv2.3
. The file-based redirects in the file metadata need to be updated for this solution to work.This PR cannot be merged until we receive confirmation that the customer email has been sent.
Affected docs
Testing
See staging build to test the following scenarios:
All 2.0 URLs
2.0 redirects from metadata