To perhaps help us push out releases in a more timely fashion, maybe we should start making release Milestones? We've had them in the past: https://github.com/apache/trafficcontrol/milestones I don't think deciding on what we
want in 4.0.0 is realistic right now, but we could certainly start planning for 3.0.1 and even 3.1.0. Adding issues to fix or Pull Requests to include would probably be a voting process (a cursory reading of the ASF release candidate process suggests that the votes for merely planning a release need not be "binding", though I could very well be wrong about that). Honestly, for a patch version we should probably only look at things that are actually done, whereas for a minor version release we'd want to plan on including fixes for extant problems and including functionality that may not be written today. Making sure everything that goes into a release is tracked by a milestone as progress is made will also simplify checking the changelog for everything that should be there/maybe even generating the changelog from the milestone. I don't have the authority to create milestones, which suggests that even doing that requires a vote from the community before any committers feel obligated to do anything. I'm +1 on creating milestones for 3.1.0 and 3.0.1, and if and when voting on those commences I have some candidates for inclusion in each to propose.
