I’ve posted next steps to the cpan-workers mailing list and started a discussion thread for each of the 34 proposals listed below. To join in the discussion, join cpan-workers by emailing cpan-workers-subscribe@perl.org.
Formatting and Schema
- 01. Update the YAML version declaration
- 02. Formally switch to “YAML Tiny”
- 03. Deprecate YAML Tiny dialect for JSON
- 04. Formalize allowed version number formats
- 05. Schema
- 06. Data structures, not YAML
Prerequisites
- 07. Enhance granularity of prerequisites
- 08. Extensibly Group Prereqs
- 09. Clarify intent of ‘recommends’ and add ‘suggests’
- 10. Add a free-text prerequisite field
- 11. OS/arch/platform-specific requirements
- 12. Allow Sequences (Arrays) for Prereqs
- 13. Add a post_depends set
- 14. Prerequisites should be mutually exclusive
- 15. Add development_requires
- 16. Binary Package Dependencies
Change or clarify existing fields
- 17. Better formalization of license field
- 18. Make dynamic_config mandatory
- 19. Make repository resource a hash
- 20. Make bugtracker resource a hash
- 21. Formalize optional_features
- 22. Clarify author field
Add new fields
- 23. Have a “development version” flag
- 24. Add a “release_status” field
- 25. Controlling test suite runs
- 26. Specify a DLSIP resource
- 27. Long description
- 28. Short description
- 29. Language
- 30. Trove-Like Categories
- 31. Version changes
Other proposals