xmlsec / python-xmlsec

Python bindings for the XML Security Library.
MIT License
95 stars 99 forks source link

Remove tumbleweed ci workflow 🔥 #333

Closed jonathangreen closed 2 weeks ago

jonathangreen commented 3 weeks ago

The tumbleweed CI workflow was failing because we needed to specify --non-interactive to zypper and remove the now unsupported python 3.8 version.

Based on the conversation on this PR, it has been updated to just completely drop the tumbleweed CI tests.

agronholm commented 2 weeks ago

Any idea why this workflow even exists?

jonathangreen commented 2 weeks ago

Nope! I'd be happy to just see it be deleted 🔥

agronholm commented 2 weeks ago

On another note, do you know any way to reach the developers, like Discord, Gitter, IRC...? There are several aspects of the project I'd like to discuss with them.

jonathangreen commented 2 weeks ago

I don't. I think @jimjag is the person to talk to. I'd suggest maybe making an issue in the tracker and pinging him there.

jimjag commented 2 weeks ago

I agree that tumbleweed should be removed. Maybe we should just do that and close this PR

agronholm commented 2 weeks ago

Would you be open to a more comprehensive, sweeping clean-up of the test workflows? Also, how do you do releases? I have my own very nice workflow for that which you could adopt if you want to.

jonathangreen commented 2 weeks ago

@jimjag @agronholm I updated this PR to just drop this workflow.

jimjag commented 2 weeks ago

@agronholm Yes, as long as we are cleaning up workflows, would love to see what you have in mind.

agronholm commented 2 weeks ago

I'll tinker with my own fork for a while. I'll open a new PR when I have something worthy of merging.

agronholm commented 2 weeks ago

One more question – do you still intend to support all these obsolete Python versions?

agronholm commented 2 weeks ago

Is there a chat forum where I could talk to you guys in real time?

agronholm commented 2 weeks ago

Tinkering with the build process turned out to be much harder than I expected. I noticed that the process involves creating both static and dynamic builds for all platforms. What's the rationale for this, and is this something you still want to keep doing?

agronholm commented 2 weeks ago

@jimjag you forgot to remove the badge in the README.