On 12/03/2019 10:18, Victor Stinner wrote: > Le sam. 9 mars 2019 à 14:00, Michael <aixto...@felt.demon.nl> a écrit : >> I was actually think more of the backporting from master to 3.7 and 3.6. >> It was made very clear to me well over a year ago that "nothing" would >> be considered for 2.7. However, the issues I have been fixing have been >> around forever. I guess I was not smart enough to "request" a backport >> for the previous issues. >> >> Not trying to be a burden for anyone - is it worth looking into? I could >> try some "simple" merges. Most of the changes are closer to typo's that >> anything else. > 3.6 now only accept security fixes. > > I don't think that it's worth it to touch Python 2.7 which is close to > its death. > > I'm not interested to spend time on backporting AIX-specific changes > to 3.7. I dislike introducing too many changes in a stable branch. My > experience tells me that any single change can introduce a regression. > I suggest to focus on the master branch. > > I'm telling about Python upstream. You can easily maintain your > CPython fork for patches on 2.7, 3.6 and 3.7. It's very common that > packages of a Linux distribution include downstream patches. I know > that well, I'm working for Red Hat and we have between 12 and 55 > patches per Python package :-) > > Maybe you will find someone else to do the backport ;-) > > Victor > Understood - and have, after I better understood the reluctance for any AIX related patch - took, I think it was yours (Victor) advice - worry about master, and when that is done (all test pass) - re-evaluate.
I have also already started maintaining my own forks for 2.7, and for a while 3.4 through 3.6. I have no issue doing the backports myself. I might need to learn some tricks with git to make it nearly automated, but I do not want to have the expectation that they will be considered, when in fact, there seems to be more aversion than willingness to accept. I too am a volunteer. I have no commercial benefit from anything I have done. Nor do I expect any from any future action. No manager of mine is encouraging me to do this - so no "bonus" at all. I hoped I was contributing. The last few messages have discouraged me in ways that months of discouraging messages from many sources never did. I choose to ignore those messages. But now the 'fire' is out. I gave my word, and shall keep it. But only if I feel there is some level of acceptance. If you really do not want AIX supported - I am finally ready to accept the hint. I'll leave you all alone (and wish you well). So, to get back to core question: If I backport the patches to the failing tests will they be considered for merge? Sincerely, Michael p.s. I am responding here as my gut says it has the smallest following. I am not looking for any 'distress' with anyone.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
