First of all: Thank you for helping to make Crystal available in downstream package repositories. It’s much appreciated.
I’m reaching out to the maintainers of Crystal packages because I’d like to start a conversation about how we could better connect and ask how we could improve the packaging workflow for Crystal.
For example, sometimes we need to communicate changes that affect packaging in an upcoming release. We usually mention that in the release notes, and the release pre-announcement published on the Crystal forum.
As a current important notification, the upcoming release 1.22 requires requires 1.14 or higher as bootstrap compiler.
I believe it would be great to have a dedicated space for coordination and collaboration between upstream and downstream projects, as well as between downstreams from different ecosystems.
Discussions about packaging are already happening in different places, such as the Crystal forum, random GitHub issues, and other channels. Having a dedicated space would improve exposure and accessibility.
Now the question is how would that look like? What communication tool would you prefer?
My preference would be a dedicated category in the Crystal forum. Most community members are already there, the infrastructure exists. Active participation requires a forum account, but you could passively read and subscribe to RSS feeds.
But I’m open for your suggestions. If you prefer an open mailing list, for example, we could consider that.
Maybe we can borrow established good practices from other communities, so I’m eager to learn about that.
I’m posting this topic in the forum as a starter, but I’m also reaching out directly to known maintainers of Crystal packages which do not have a forum account. I’ll forward any responses from those direct communications.
Hi, I’m a maintainer of the crystal package in Alpine Linux. I’ve just registered to this forum. However, I’m not planning to actively monitor it. If you create a topic I can subscribe to and receive email notifications, it’s perfectly fine with me.
Thanks for reaching out! I definitely appreciate the communication. I, for one, don’t want to burden the core team with extra administrative overhead.
Speaking from the Fedora packaging side, a proper, standardized CHANGELOG is, honestly, most of what downstream packagers need. Even better would be a living changelog in git ([Unreleased]) with a dedicated packaging/build section covering bootstrap compiler bumps, LLVM compatibility, changed build flags, and C dependencies. That allows packagers to see breaking requirements coming well in advance.
Paired with a simple Pre-Release/RC forum announcement that packagers can “Watch” to receive an email notification (allowing us to test in distribution chroots before the final tag is stamped), that gives us everything we need without creating extra overhead for the core team.
If I may, I’d like to suggest: Keep a Changelog. I’ve been using it for a while now (in reStructuredText form) and I find it helpful, well organized and well thought out.
Thanks for all the replies. There were a couple of responses via mail as well.
While some would prefer a mailing list, everyone was on board with using the forum for this. So let’s go with that.