Skip to content

Pegasus and WebMetal announcements, plus gfx-0.13 #358

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 19, 2016

Conversation

kvark
Copy link
Contributor

@kvark kvark commented Dec 18, 2016

No description provided.

@kvark kvark changed the title Pegasus and WebMetal announcements Pegasus and WebMetal announcements, plus gfx-0.13 Dec 19, 2016
@nasa42 nasa42 merged commit 9d2e20e into rust-lang:master Dec 19, 2016
@kvark kvark deleted the patch-3 branch December 19, 2016 19:18
@nasa42
Copy link
Member

nasa42 commented Dec 21, 2016

Hi @kvark, after some thought, I've decided to remove Pegasus and gfx-rs announcement lines as we no longer publish New Crates section and release 0.13 doesn't seem to be a major change.

Thanks for the PR!

@kvark
Copy link
Contributor Author

kvark commented Dec 21, 2016

@nasa42 I wonder why you stopped doing the "New Crates"?

gfx-0.13 may not be the biggest release in history, but we've got quite a few features shipped (transform feedback, persistent mapping, proper errors, and Metal backend), so it's far from a maintenance release either. I don't mind the policy of limiting the project updates in general, but it seems quite unfair to me that various This Week In XXX posts are getting into TWIR without questions, while the scale of changes is incomparable to gfx-0.13, given that it's been developed for 5 months since gfx-0.12.

@nasa42
Copy link
Member

nasa42 commented Dec 26, 2016

It's a bit of a blurred line between what qualifies for inclusion and what doesn't. I'm sorry that it looked unfair to you that your crate news was not included.
The other weekly news articles are added mostly because of convention as they have been a continuous feature of TWiR for more than a year.
I really don't have a specific set of objective criteria on what to include and what not to, and it mostly falls down to my own subjective opinion. We should come up with a notability guidelines for TWiR, but unfortunately I don't have a complete answer on how to define that.

@kvark
Copy link
Contributor Author

kvark commented Dec 26, 2016

@nasa42 👍 for notability guidelines
Since it would be fairly difficult to formalize them, we could at least make them simple. For instance - no crate updates. At the end of the day, it's crate author's call to whether announce an update or not. And if they consider the update to be notable - they need to crate a blog post of sorts, which automatically includes all the TWiX.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants