-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feat(docs): 1.7 blog post #3264
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
7 Ignored Deployments
|
🟢 CI successful 🟢Thanks |
ccffc4b
to
7220733
Compare
ea2a735
to
cd6df5d
Compare
'jaredpalmer', | ||
'mehulkar', | ||
'chrisolszewski', | ||
'nicholasyang' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just curious... are we just copy pasting everyone onto every post? seems like it would be nicer / more meaningful if we filtered this list by whoever's actually writing (and acknowledge code contributions in the post itself if we want to do that)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The whole team is typically involved with the release blog posts in some aspect (from writing to reviewing to publishing) - so it's simpler in my opinion to list the core team as the authors. Plus we're all hashing out all the content day to day as a team anyway. We're a team and we're all involved here.
For the more specific one offs (like https://turbo.build/blog/turbopack-benchmarks) I think those make sense to list writing authors only.
I could be convinced otherwise as well, but I don't really feel the need to be pedantic about the bar for entry to a release post.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, just gut checking :).
We're a team and we're all involved here.
💯 💟
Blog post for turbo@1.7