Re: how to manage d/changelog for updated but not yet sponsored package
> Depends on the situation. If it's a quick update, and I can followup
> within moments, then indeed, there is no reason to increment the version
> (see my "when it makes sense" comment above).
> But if hours, or even days can pass between iterations, then I much
> prefer a new version on mentors. That also has the advantage of me not
> neccessarily being a bottle neck, and another sponsor can review it and
> perhaps sponsor it too.
Hmm, another sponsor also could look at commits in VSC to observe changes since
last message. Isn't it?