"GitHub Package Registry will support Swift packages" is misleading 5 years later

[vmanot]

This blog post (published June 3, 2019) advertises "GitHub Package Registry will support Swift packages".

It's been more than 5 years since this was published, and as such is well into false advertisement territory, IMO.

[novium2]

Seems like a lot of people also want that to be available. We do try and use these forums to surface feedback to the dev teams; can you tell me any more about how this impacts you and your work?

[vmanot]

@novium2 there's already a thread for that here: https://github.com/orgs/community/discussions/36327

My intention with this thread was to flag what I believe to be (without speculating why or how) a very misleading blog post, and to urge GitHub to rectify the situation by updating the post.

While I am happy to discuss and shed light on how the lack of this feature impacts me or my fellow Swift developers, I do not want to change the focus of this thread from "this article ought to be updated to accurately reflect the state of tings" to "tell us more about the Swift Package Registry". That discussion is better suited for #36327, discussing it here would detract from the issue that I'm raising.

Having clarified that, if you feel that this feedback (which is more of a bug report about something that is rather than a discussion around a feature request around something that isn't) is better suited elsewhere - please let me know, I'll repost/resubmit it.

[novium2]

So I don't want to set inaccurate expectations - this really is just a forum to let users swap tips and share experiences and feedback, and I am just a moderator- but it definitely helps to raise new issues sometimes rather than tagging into ones that may be more than a year old because of the way it shows up in the data.

I can definitely pass your feedback on, but I suspect that updating old blog posts isn't likely to be a high priority for the communications team. I don't think the intent was to mislead; I wasn't at the company then, but I bet you dollars to donuts it was on the roadmap and just fell off for some unforeseen reason. Which is why I think it's important to share this feedback and to raise the visibility of the ask; product managers are always having to balance many competing priorities, so talking about it and having it show up in the data can have an impact.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐