Re: Changelog
Posted: 22 May 2018, 10:44
> How would he be most affected? (I get the idea that you think this will a lot more work for devs when it really isn't.)
Well, I assume he will at some point pick up merging PRs to a significant degree. And this is more work for the person who is doing the merging/reviewing. He has to check if the changelog entry is there (and up to our standards) and he has to handle potential merge conflicts.
Now that is only a small task, but it has to be performed on every single PR and piles up onto the various other little tasks that need to be handed during the merge process. Personally I find that this kind of little tasks is wearing me down quite a lot (if they exist in significant numbers); a lot more than having everything batched up into one larger task that I can do all at once. Of course that is only my personal opinion. I don't know how scrawl feels about it. That's why I suggested to wait for him to state his opinion.
Well, I assume he will at some point pick up merging PRs to a significant degree. And this is more work for the person who is doing the merging/reviewing. He has to check if the changelog entry is there (and up to our standards) and he has to handle potential merge conflicts.
Now that is only a small task, but it has to be performed on every single PR and piles up onto the various other little tasks that need to be handed during the merge process. Personally I find that this kind of little tasks is wearing me down quite a lot (if they exist in significant numbers); a lot more than having everything batched up into one larger task that I can do all at once. Of course that is only my personal opinion. I don't know how scrawl feels about it. That's why I suggested to wait for him to state his opinion.