Given that we are in the midst of redefining our release process and my recent experience with publishing v1.4 release announcement blog post, I want to propose to establish a process of writing blog post that will be combined with version release.

Even though I started working on blog post ~2.5 weeks before target date I still had to do a lots of begging and bugging. Especially sig-docs folks gave a hard time, and asked in the future to put out post draft PR at least 2 weeks before publishing target date.

My suggestion:

1. Require feature owners that are to be included in the new version release to submit a small write up before new Gateway version gets released.
2. Have a system to assign blog post owners in advance, person who will take on combining all the write ups and adding intro/outro, and working with sig-docs folks for timely release (that is 30 days after version release).
   • we can use round robin or some other system.

Also, if we are splitting standard and experimental releases, my thoughts are for standard release. But do we need announcements for monthly experimental releases?