Open haarg opened 9 years ago
+1
I saw some discussion about this being a boolean field for the dist. Is there any plan for deprecating just one module within a distribution or is that not a common enough use case?
@dagolden suggested handling per-module deprecations via x_deprecated fields in the provides hash. I think this is a sensible solution.
Once people start using this, could someone update this ticket with a couple of example dists that we can work from?
Is there any plan for deprecating just one module within a distribution or is that not a common enough use case?
Yes, I've got this feature written for Dist::Zilla::Plugin::Deprecated, and will release it as soon as the necessary change to CPAN::Meta::Merge is released (likely at/by Berlin).
@oalders these distributions now have individual modules marked as deprecated (vs. the entire distribution):
https://metacpan.org/release/Dist-Zilla-Plugin-Test-EOL https://metacpan.org/release/Dist-Zilla-Plugin-Test-NoTabs
@karenetheridge I don't see x_deprecated in https://metacpan.org/source/ETHER/Dist-Zilla-Plugin-Test-EOL-0.17/META.json Am I looking at the wrong release?
yes, it's 0.18, just uploaded. :)
Ah. I see it in https://metacpan.org/source/ETHER/Dist-Zilla-Plugin-Test-EOL-0.18/META.json Thanks!
now that we have the field in the metadata, this can be done.
It would be nice if deprecated distributions didn't show, or are masked/greyed out, in search results by default so that the user can ignore them.
I had a conversation about this feature yesterday with @neilb at LPW, but it looks like MetaCPAN doesn't yet make use of the deprecated flag.
Has a decision been made regarding what exactly we'd like to do with these distributions / modules? I imagine we want to mark them as deprecated in both the search result page and the module page. But how?
Also, would we want to do anything to further reduce their visibility in search like @bluefeet suggested? I'd like to see them at least ranked lower in search results, but we could even hide them entirely unless the search was for the literal name, or the user specifically asked for them (eg. clicking on some "include deprecated modules").
If that was clearer, I think I could try putting something together.
In #toolchain, there has been discussion of establishing x_deprecated as a field to indicate deprecated modules. In the future, this could be used in search ranking. Initially though, it would be good to add a visual indicator of this somewhere when viewing modules.