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 as the email announcem
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
https://issues.apac
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 wrote:
> As discussed
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 release.
Agree, and 1/ should already be part of the announcement e-mail (at a very high
level).
Regards
JB
On 01/29/2018 06:41 PM, Daniel Kulp wrote:
> Personally, I would like to see two things:
>
> 1) A “shortish” announcement blog post that describes at a very high level
> the new things. This rea
Personally, I would like to see two things:
1) A “shortish” announcement blog post that describes at a very high level the
new things. This really can just be the release notes.
2) If there are big “really cool” things that deserve more attention (and a
developer willing to give it said atten
+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, which
+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 projects do. But as JB sai
+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 way
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, Ca
This is a fork of a recent message I sent as part of the preparations
for the next release.
[tl;dr] I would like to propose that we create a new blog post for
every new release and that this becomes part of the release guide.
I think that even if we do shorter releases we need to make this part
o
11 matches
Mail list logo
