We can surface data about a Project future releases. Open Source Projects define tentative dates for the next minor/major releases and communicate these to their ecosystem and users so they check their alpha/beta/rc versions and can stop a potential breaking change that would be hard to correct later. This data is currently ad-hoc per project.
If we have these events as records in the project PDS, tools like ecosystem-ci can use this data to automatically notify the right stakeholder when there is a regression. Instead of the Project maintainers pinging downstream maintainers manually, they will get a "[project] is going to release its next major in two weeks, there are three regressions in your CI" with links to each error, and a link to where they should chat/connect with the Project maintainers if they need help or have feedback.
Apart from releases timing, we could also have release notes (it could be a link to the GitHub release notes), or also direct notes in the record.
We can surface data about a Project future releases. Open Source Projects define tentative dates for the next minor/major releases and communicate these to their ecosystem and users so they check their alpha/beta/rc versions and can stop a potential breaking change that would be hard to correct later. This data is currently ad-hoc per project.
If we have these events as records in the project PDS, tools like ecosystem-ci can use this data to automatically notify the right stakeholder when there is a regression. Instead of the Project maintainers pinging downstream maintainers manually, they will get a "[project] is going to release its next major in two weeks, there are three regressions in your CI" with links to each error, and a link to where they should chat/connect with the Project maintainers if they need help or have feedback.
Apart from releases timing, we could also have release notes (it could be a link to the GitHub release notes), or also direct notes in the record.