chennes wrote: ↑Thu Jul 28, 2022 2:06 am
Will do - I didn't know how closely you wanted to control it. Obvious backports I will take care of, then. Do you want me to post about them here?
Thanks!
I think every developer should backport directly. I fully trust my colleagues
When you backported something, just update the list in the initial post of this thread. I use this list to generate the changelog for the point releases.
easyw-fc wrote: ↑Fri Jul 29, 2022 3:21 pm
if possible this would be useful too
This does not seem to be a bugfix.
However, I tried to backport nevertheless but got merge problems. The STEP code had been changes a lot it seems. Therefore I think it is too risky.
chennes wrote: ↑Fri Jul 29, 2022 3:12 pm
The list of fixes is getting pretty long
I see that too and the list was growing quicker the recent weeks, therefore I waited a bit longer than the 4 weeks after the release that I had in mind.
uwestoehr wrote: ↑Fri Jul 29, 2022 10:44 pm
However, I tried to backport nevertheless but got merge problems. The STEP code had been changes a lot it seems. Therefore I think it is too risky.
Is it better to rename this topic to [Tracking] Backport commits to 0.20.1 branch so that after the release you can lock the topic and start over with [Tracking] Backport commits to 0.20.2 branch etc?
Jee-Bee wrote: ↑Mon Aug 01, 2022 8:29 am
Is it better to rename this topic to [Tracking] Backport commits to 0.20.1 branch so that after the release you can lock the topic and start over with [Tracking] Backport commits to 0.20.2 branch etc?
As for 0.19, the thread will be used for the whole release cycle. This way we can refer to the fixes easily in forum discussions etc.