chore(blog): add release notes for 2.2 september release #324
Conversation
|
✔️ Deploy Preview for asyncapi-website ready! 🔨 Explore the source changes: 09de30a 🔍 Inspect the deploy log: https://app.netlify.com/sites/asyncapi-website/deploys/6153133002db300007a2ea3c 😎 Browse the preview: https://deploy-preview-324--asyncapi-website.netlify.app |
|
release note entries for
|
pages/blog/release-notes-2.2.0.md
Outdated
| Are you wondering how we managed to release 2.2.0 release just three months after 2.1.0 release? I recommend you familiarize yourself with [AsyncAPI release process](https://github.com/asyncapi/spec/blob/master/RELEASE_PROCESS.md). Brace yourself for the next release scheduled for January 2022. | ||
| <img className="w-3/4" src="/img/posts/release-notes-2.2.0/brace.webp" /> |
There was a problem hiding this comment.
I think 3.0.0 will probably come out in April, not January :) We still don't have conclusions about receive/send proposition and many others, and let's not forget that 3.0.0 will involve breaking changes in parser, generator, templates, react-component etc, so a lot of work. Generally we should not give hope to people that 3.0.0 will come out in January and this meme points to it 😅
There was a problem hiding this comment.
Meme doesn't say anything about January. Also its point is not to give hopes, but "brace yourself", so be aware that it is coming, and there is really no other way, a workaround to not do it
There was a problem hiding this comment.
maybe I just modify sentence Brace yourself for the next release scheduled for January 2022. to The next release scheduled for January 2022. The next releases are later in April, June and September.
There was a problem hiding this comment.
there is no way we release 3.0 in January 😄
There was a problem hiding this comment.
I just pushed improvement, you should be happy
There was a problem hiding this comment.
Yeah, this second sentence is better :)
There was a problem hiding this comment.
Actually, you have a typo. Should be The next release is scheduled for January 2022. Would it make sense to involve @alequetzalli this time? I'm more than sure we will learn a lot about wording release notes, at least I will 😅
There was a problem hiding this comment.
well, grammar improvements, definitely 🙏🏼 . Change in wording and style? no plans really, I sign it with my name ❤️ , happy to see the next release someone else doing it 😄 release coordination is a role anyone can take up 😉
There was a problem hiding this comment.
hahahaha "release coordination is a role anyone can take up" 😂
I love helping w/ release notes because it helps me really learn in better detail the many items being shipped around me. If you want me to switch off and on with you, I am happy to help out! Or if you like doing it just fine and think you would feel good about a 2nd pair of eyes for quick grammar review or thoughts of improvements, I guess just let me know?! 😀😂😁😆
There was a problem hiding this comment.
I'm definitely up for a grammar review. Switching of roles just for release notes writing, not sure as release coordination is complex already. We might consider it for the next release. For this one, all is ready, no new things are coming in.
Co-authored-by: Alejandra Quetzalli <[email protected]>
quetzalliwrites
left a comment
quetzalliwrites
left a comment
There was a problem hiding this comment.
Ok @derberg, I did the review !! ✨✨🦄
Co-authored-by: Alejandra Quetzalli <[email protected]>
6 participants
This is a placeholder draft of release notes for upcoming 2.2 release.
It might of course happen that eventually nothing will be introduced in september release cycle and this draft will be closed without further work