Re^18: Fixing broken CPAN modules without author cooperation (patch)

[tye]

in reply to Re^17: Fixing broken CPAN modules without author cooperation (patch)
in thread Fixing broken CPAN modules without author cooperation

Frankly, that'd suck as persuasion.

But it got me to think about your proposal for a moment longer and to realize it is also just the wrong place to store such information. So "thanks" for that. If I realize that my typical response time is faster/slower than I previously thought, then I'm supposed to upload new releases of all of my modules to note that? No thanks.

[Anonymous Monk]

If I realize that my typical response time is faster/slower than I previously thought, then I'm supposed to upload new releases of all of my modules to note that? No thanks.

Well, it doesn't have to work like that. It can just be advisory note, last known interval (or whatever you call it)

It has the benefit of being public and available apart from PAUSE (available to MetaCPAN) and traceable on a per release basis

If you update it after releasing a tarball, the final/authoritative metadata can be stored in authors/id/T/TY/TYEMQ/ReleaseSchedule.json
authors/id/T/TY/TYEMQ/TYEMQSAYS.yml
authors/id/T/TY/TYEMQ/TYEMQSTATUS.yml
authors/id/T/TY/TYEMQ/TYEMQSELFRATING.json
authors/id/T/TY/TYEMQ/Acme-ESP-1.002006.lastmeta

Under some name that makes sense -- this is what I'm asking you write, the spec/terminology/description (you already wrote a general description)

Though even the tarball itself could be updated :) ( probably considered a bad idea )

update: See also Project Metadata Model/ Description of a Project