Good points Jarek. I mentioned it in the initial email, but I think we should keep it optional to start with. I'd rather get the basics in place first, as I think we are going to find some interesting scenarios as we try and put rules around it. Even if only release managers touch it in the short term, we still benefit from it (or at least I will).
I have every intention of making it required down the road. I'm eager to help spread the changelog workload around a bit more :) Just a single example of where things can get interesting is due to our monorepo: setup.py changes could require a core newfragment, a provider newsfragment (when we get there), or both. I'm sure we can sort it all out, but I don't think we need to wait and have it all on day 1. We will end up needing to handle 2 sources of changelog entries in the short term regardless (and is part of my todo list). My gut tells me we should do this incrementally instead. As long as we "catch up", when we start requiring it shouldn't matter (the 2.3.0 fork is a natural time, but we don't have to hit it dead on). In fact, I'll likely start putting requirements on the helm chart first, as it is more isolated.
