[DOCU-745] List of deprecated classes, methods and templating functions Created: 10/Jun/16 Updated: 12/Jun/20 |
|
| Status: | Reopened |
| Project: | Documentation |
| Component/s: | content |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
Requested by moabdelhadi at "Unconference 2016 - Migration 4.5 -> 5.x" session:
The format of the report could be a table with two columns:
We have some of this already in the migration documentation but the information is spread out and does not cover every major version increase.
Idea: Make the deprecation report a standard section in release notes for every major (x.y) version of Magnolia. |
| Comments |
| Comment by Christoph Meier [ 02/Dec/16 ] |
|
ahietala I rather recommend creating a new page - and from now on mentioning classes when they become deprecated - starting with the next release. Some classes we encounter again and again - e.g. by customer request or from forum questions etc., we may add on a agile process. However, we can invest some time and searching through code repositories to get an idea how much deprecated code we have. |
| Comment by Julie Legendre [ 30/Sep/19 ] |
|
In order to better focus our efforts on DOCU tickets that are still relevant and important, all tickets older than 18 months have been labelled as outdated and are being automatically closed. |
| Comment by Antti Hietala [ 07/Oct/19 ] |
|
Let's do a timeboxed research. Ability to see a list of deprecations between major versions (6.1 to 6.2) in one place is a fairly common feedback from clients. It allows you to estimate and budget upgrades. Ideally, we would scope and automate this task so that it is not a manual discovery effort for Doc Team or for the clients. |