As discussed on https://gitlab.eclipse.org/eclipsefdn/marketing/-/issues/2298, we'd like to have an RSS feed for new project releases that the marketing team can use to send "project news alerts" on our social media channels. We currently have this for project proposals. Is this something that can be reasonably set up?
As far as I know, there is no guarantee that the project will deliver on these plans.
@wbeaton While we are tracking release date, can we safely assume that projects will publish that release on that day? My concern here would be that the marketing team start promoting a release on social media that never occurred.
@wbeaton While we are tracking release date, can we safely assume that projects will publish that release on that day?
Nope.
My concern here would be that the marketing team start promoting a release on social media that never occurred.
Yup.
What I'd like to do is start harvesting release information from GitHub and GitLab. Those map to actual releases. I haven't had to time to investigate this.
The release tracking functionality in the PMI is used correctly by a handful of projects. You can, for example, be fairly certain that the release information provided by projects that participate in the simultaneous release provide good information.
We built this functionality before GitHub had any notion of releases. So this is a case of the PMI functionality is no longer providing a lot of value for projects and so keeping it up to date is not a priority.
Thanks for the background on this @wbeaton. Currently it looks like our best option for announcing project releases on social media might be to use the list of project releases that you approve for publishing in the community newsletter, and publish the list on EF socials at the end of the month. That way we can verify that the releases actually happened without giving more work to the projects team.