Hello,
I happen to maintain some applications in Fedora where I am strongly confident
our users would prefer "latest and greatest" over 100 % "stability" of the user
interface and/or results.
For some of them, I've been more or less silently breaking the Updates Policy
hoping that nothing would break (nothing did so far). For others, I've
requested FESCo exceptions for individual updates. I'd like to request a
*permanent exception* to allow upgrading the following tools and apps to latest
versions in stable Fedora releases.
For transparency reasons, I've decided to share the list of packages on this
mailing list before approaching FESCo. If you see potential problems, do let me
know.
PrusaSlicer and Cura (3D printer control apps)
==============================================
- prusa-slicer
- cura (and dependencies):
- CuraEngine
- cura-fdm-materials
- libarcus
- libnest2d
- libsavitar
- python-pynest2d
- python-uranium
IMHO users want the latest features to support their latest 3D printers and
having an outdated version only makes them reach for an alternate source of
PrusaSlicer / Cura.
Black (Python code formatter)
=============================
- python-black
See also https://pagure.io/fesco/issue/2259 and https://pagure.io/fesco/issue/2525
Black is a code formatter with very strict rules. One of the benefit of using
black is the determinism of its output. By running black on code twice, it is
guaranteed (well, claimed) to produce no changes. When updating it however, new
changes might appear on a codebase that was previously considered "OK".
With each release, there might be several subtle changes in formatting, however
I expect users who install black from RPM to prefer the latest version of black
over total stability of its output. Who needs 100 % stability can "pin" exact
black version in their requirements / pipenv /poetry file and get it form PyPI.
Tox (standardized Python test executor)
=======================================
- python-tox
Tox aims to automate and standardize testing in Python.
As new standards happen, tox is adapted upstream. It very rarely breaks
backwards compatibility. Unlike other Python development tools, it is much more
beneficial to have tox installed in the system Python stack and not in a
virtual environment. I'd like to always provide the latest and greatest tox to
our users = Python developers.
Note that this exception would not apply to the planned entire rewrite (i.e.
tox version 4), only to latest tox 3.
HTTPie (command-line HTTP client)
=================================
- httpie
"HTTPie is a user-friendly command-line HTTP client for the API era. It comes
with JSON support, syntax highlighting, persistent sessions, wget-like
downloads, plugins, and more." The command line interface is generally very
stable and the upstream developers are very interested in seeing the latest
version in stable Fedora releases (and eventually also EPEL, but that is out of
scope here).
ownCloud Desktop Client
=======================
- owncloud-client
As OwnCloud serves are updated, users might need the latest version of the
client installed to be able to use them. Hence, I'd like to be able to update
this package freely.
OTOH I don't actually plan to do that often, because I maintain the package "to
scratch my own itch" and I would only do that if the server used by our
university requires client updates. However, if co-maintainers appear, this
could happen more often.
Thanks for any feedback.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
