Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[3.0] Remove all deprecated articles and versionadded directives#5585

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

wouterj
Copy link
Member

Let's clean up with 3.0 docs!

I don't think we should have BC links for articles that are marked for deprecated in the 2.x docs, people will simply have to link to the 2.x docs instead in such case.

QA
Doc fix?no
New docs?no
Applies to3.0+
Fixed tickets-

Thechoice_list option was not yet removed, as we first have to document the replacements (see#5179)

@@ -112,24 +106,14 @@ The actual default value of this option depends on other field options:

.. include:: /reference/forms/types/options/mapped.rst.inc

.. _reference-form-option-max_length:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Seems like this is referenced from a cookbook article.

@stof
Copy link
Member

stof commentedAug 1, 2015

@wouterj the issue with not having BC links is that many existing links are probably linking to/current (which is the right way IMO as linking to a specific version would mean you link to unmaintained doc when time flies). So we should try to preserve BC for URLs (which is also why it would be very nice to have the redirection map working on a per-version basis /cc@javiereguiluz)

wouterj added a commit that referenced this pull requestDec 5, 2015
…ent (ogizanagi)This PR was merged into the 3.0 branch.Discussion----------Update 3.0 docs accordingly to min PHP version requirement| Q             | A| ------------- | ---| Doc fix?      | yes| New docs?     | no| Applies to    | 3.0+| Fixed tickets |#5947I'm not sure about the politic regarding the removal of anything mentioning earlier version of PHP for the 3.0 docs ? Should it be reverted ?Regarding this PR:#5585, it's seems coherent to me to do the same for PHP versions.Commits-------d577848 Update docs accordingly to min PHP version requirement
@wouterjwouterj closed thisFeb 7, 2016
@wouterjwouterj deleted the remove_versionadded_deprecations branchFebruary 7, 2016 17:25
xabbuh added a commit that referenced this pull requestFeb 9, 2016
This PR was squashed before being merged into the 3.0 branch (closes#6242).Discussion----------Removed all 2.x versionadded directivesReplaces#5585Commits-------f8b560d Removed all 2.x versionadded directives
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

4 participants
@wouterj@stof@xabbuh@javiereguiluz

[8]ページ先頭

©2009-2025 Movatter.jp