Hi @looo
Sorry but that just ain’t going to work. I was preparing a PR, for shutting down the Travis instance over the weekend and this just feels off. You have invested way too much effort in packaging during the development cycle and now is the time to profit from all that work.
I remember when i was still a somewhat fresh FreeCAD member, there was a logo competition i participated in. At that time i didn’t know yet, the challenge itself was important, and not the outcome. In the following years that logo competition ended up being a guide for me, it gave me understanding on when the peak was reached and when i started the descend on the other side. Making way for new people, to reach the same.
Now what i am trying to say is i am coming back, from the other side, will carry you over if needed. Let me stand with you on that peak again. Can you do that for me?
Take a week off, if you are not under some corona lock down, result to things like the paragliding, just please stay safe. I will hold off the PR until May. Hopefully by then we won’t be toying with the release anymore and some more certain time frame will be known.
In addition i feel that you need to be there, finishing the migration to new module structure. Once the next development cycle start, please create a PR, obsoleting the old module style support, and let others sort out the porting over during the course of the next development cycle. It would be nice if you would provide some general guidance, for people here asking. There is an army of new developers now, they like pep8, like to restructure modules, please, give them some work. As for the modules that won’t make the transition, that’s life, it happened once already, Py2/Qt4 → Py3/Qt5.
And we are finally entering the Py2 free development cycle, and you would leave now?
C’mon, give me something?