Re: [PROPOSAL] Add a blog post for every new release

We could also create a GitHub label for PRs that should be looked at when crafting the next release notes, applied per committer discretion. On Fri, Feb 16, 2018, 2:36 PM Robert Bradshaw wrote: > Huge +1 to proper release notes, which may make sense as blog posts as > well

Re: [PROPOSAL] Add a blog post for every new release

Huge +1 to proper release notes, which may make sense as blog posts as well as the email announcement. Yes, we have the Jira "release notes," but they are only one step above the git commit logs, and generally hard to digest (especially for an outsider). For example, if I go to

Re: [PROPOSAL] Add a blog post for every new release

Thanks Ismael - I've added a couple of the major things I know. I tried scanning the whole git shortlog for major things, but it was too much, so probably better if individual committers make their contributions to the document. On Fri, Feb 16, 2018 at 9:01 AM Ismaël Mejía

Re: [PROPOSAL] Add a blog post for every new release

As discussed in this thread I created an initial version of a document for the release notes. Feel free to add/include details that you consider worth (+correct my english mistakes) or new sections/ideas. Remember the idea is to have a concise document of the most important changes in this

Re: [PROPOSAL] Add a blog post for every new release

+1. Release notes from jira may be hard to digest for people outside the project. A short summary for may be really helpful for those considering Beam or loosely following the project to get an understanding of what is happening. It also presents a good opportunity share progress externally,

Re: [PROPOSAL] Add a blog post for every new release

+1 I like the idea and agree with adding it to the release guide. Even a very short post the length of an email is nice. We could have a template to make it very easy. On Mon, Jan 29, 2018 at 8:02 AM, Romain Manni-Bucau wrote: > +1 to have it as a best effort - most of

Re: [PROPOSAL] Add a blog post for every new release

+1 to have it as a best effort - most of projects do. But as JB said, if it slows down the release motivation it shouldn't be enforced but just encouraged. A good solution Ismael is you take this responsability for the coming releases after the release manager is done with the annoucement. This

Re: [PROPOSAL] Add a blog post for every new release

Hi Ismaël The idea is good, but the post should be pretty short. Let me explain: - We will have a release every two months now, so, some releases might be lighter than others, and it's normal - the Jira Release Notes already provides lot of details For instance, in Apache projects like Karaf,