On 06/20/2018 07:53 AM, Rafael Weingärtner wrote:
> It seems so. It can then be a part of the PR. I mean, in the PR we could
> require a commit that updates this file.
Yes, that would be the thing. When you send a PR with a change that is
'big enough' you also include updating the Pending Release Notes file.
> Of course, we need to discuss if all PRs should update it, or only
> important things should go in.
>
I think only important things and that it's up to the developer to guess
if it's important enough to go into the PendingReleaseNotes file.
Wido
> +1
>
> On Tue, Jun 19, 2018 at 11:00 PM, Wido den Hollander <w...@widodh.nl> wrote:
>
>> Hi,
>>
>> At the Ceph project we work with a Pending Release Notes [0].
>>
>> The idea is that if a developer writes a new feature or fixes something
>> that changes functionality (or adds one) she/he also updates the
>> PendingReleaseNotes file.
>>
>> That way when a new version is released it's easier for the Release
>> Manager to know what to highlight.
>>
>> Although we can try to get everything from Jira and Github Issues it
>> might be difficult to use the proper wording.
>>
>> On every release the files is cleared and people start to add again.
>>
>> Would this be something which could benefit CloudStack and make the
>> release notes easier and more complete?
>>
>> Wido
>>
>> [0]: https://github.com/ceph/ceph/blob/master/PendingReleaseNotes
>>
>
>
>
