Re: [che-dev] How we track issues/PR that are part of a release

[Sun Tan <sutan@xxxxxxxxxx>]

Now we don't have that automated ... and we don't know how much time it will take to do that. So I am +1 to manually add a PR/issue to the `kind/release` notes that should work without too much pain starting tomorrow. And we can create an epic for the mid/long road to make it automated. WDYT?

Without pain for you, who is the consumer, not producer of these issues, I might add ;-) But on a serious note: let's not add more manual process to creating a release: we're trying to make it as automated as possible. If we think having these "release notes" is important, let's invest in the technology to do it right and let's invest now.

I don't know why you call it "pain" but for once I had finished ... It took me less than 30 sec and 2% of my brain CPU to add my PR to the description of the release issue: https://github.com/eclipse/che/issues/17436#issue-660695018 as a producer ... Again I am not against automation but I would like that we have an alternative that is not too painful and that works until we have an automated process.