Closed jenweber closed 1 year ago
Name | Link |
---|---|
Latest commit | d5b0c9f1fe631f89e0ad7936c09241f31ce844eb |
Latest deploy log | https://app.netlify.com/sites/ember-blog/deploys/6494e261a69276000839e000 |
Deploy Preview | https://deploy-preview-1273--ember-blog.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site settings.
Is anyone working on a cover image?
While in theory Ember major releases are "boring" now, in the sense that they serve for deprecations, it remains a good marketing opportunity as it makes for good headlines. Especially if new features are also highlighted in this post. And these cover images make it nice when sharing links to e.g. Reddit, Twitter, etc.
I'm not a graphic designer but I can try and make something if that's desired π¬
Notes to self:
Deprecation removals included in EmberData 5.0-alpha: link to commits
Release blocker: There are no 4.x EmberData guides published to https://deprecations.emberjs.com/ however much of this content does exist in other places. We still need to get it up on the deprecation site.
ember-data:rsvp-unresolved-async
really needs some details in a deprecation guide@IgnaceMaes no one is currently making a cover image, but I love that idea! Do you have a specific idea for one or interest in making it? I think it would need to go through @wifelette for approval. She manages our trademark things.
@IgnaceMaes no one is currently making a cover image, but I love that idea! Do you have a specific idea for one or interest in making it? I think it would need to go through @wifelette for approval. She manages our trademark things.
Here's something I quickly put together. Like I said, I'm not a graphic designer, but even if it's something simple I think it can add a nice touch to the messaging.
Don't hesitate to reject it if it's not something that's wanted, or doesn't fit within the brand guidelines Ember is going for π
Hello teams, please review this blog post for your teamβs section by end of day Wednesday. It will get published on Thursday. The reason to push forward is that we need to get this out ASAP and then prepare for 5.1.
Some text to consider for social media shares: π Big news! #Ember v5.0 is here and it's leaner than ever! π Our updated versioning approach delivers a new major release after every 12 minor ones. We ship new features while ensuring backwards compatibility, making upgrades smoother. Say goodbye to major update challenges! Get the scoop on what's new and improved in Ember v5.0 on our official release notes.
Rendered
Todo
Volunteer help needed!
Known release blockers
Team Sign-off:
Add a β if you can confirm that the team has reviewed the post for accuracy and messaging.
When to merge