#1751: Links to DEPRECATED.pod et al
-------------------------------------+--------------------------------------
Reporter: Paul C. Anagnostopoulos | Owner: jkeenan
Type: todo | Status: assigned
Priority: normal | Milestone:
Component: docs | Version: 2.6.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
-------------------------------------+--------------------------------------
Comment(by coke):
First off, on the original post, there's a mention of a support policy
wiki page, but no url. I don't see this page.
The proposed solution really seems like overkill to me. Let me back up and
summarize the goals with the information.
1) provide a notification to our users with a shipped release about
upcoming removals due to deprecated items.
2) provide a way for users of old versions to migrate their code to work
on new versions.
It would be nice if #1 was in the release. It would be nice if #2 was not,
but was in the wiki.
Having a single file in the repository with EVERY compatibility change
ever (going forward) seems like overkill to me, ESPECIALLY if we then
duplicate it on the wiki (it would already be generated by "make html" and
therefore on docs.parrot.org.)
I don't see what the argument against multiple pages is. We clearly want
it segregated by parrot version; I think for our users, multiple pages (1
per version) with an index page linking to each of them is the best
approach. They are only going to care about certain items.
Paul - what problem are you trying to solve with your proposed changes?
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1751#comment:7>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
