Request for Updates Policy Exception: ruff #3197

Closed
opened 2024-04-14 13:39:33 +00:00 by decathorpe · 14 comments
Owner

ruff is a linter and formatter for Python code (i.e. a tool for developers). So it is in a similar situation as "black", for which an Updates Policy Exception was already granted some time ago.

I would like to update ruff to versions that contain technically "breaking" changes in stable branches. I expect that most developers who are using the Fedora package for ruff would prefer to get the latest and greatest version ASAP (upstream publishes releases with new features and bug fixes very regularly).

Other distribution channels that are recommended by upstream also get new versions of ruff instantly or quickly (PyPI, Homebrew, etc.) and other Linux distributions that provide first-party packages for ruff also seem to push new releases regularly, so it would be very odd for Fedora to ship old versions of something that is improving so fast.

The upstream release log is here: https://github.com/astral-sh/ruff/releases

ruff is a linter and formatter for Python code (i.e. a tool for developers). So it is in a similar situation as "black", for which an Updates Policy Exception was already granted some time ago. I would like to update ruff to versions that contain technically "breaking" changes in stable branches. I expect that most developers who are using the Fedora package for ruff would prefer to get the latest and greatest version ASAP (upstream publishes releases with new features and bug fixes very regularly). Other distribution channels that are recommended by upstream also get new versions of ruff instantly or quickly (PyPI, Homebrew, etc.) and other Linux distributions that provide first-party packages for ruff also seem to push new releases regularly, so it would be very odd for Fedora to ship old versions of something that is improving so fast. The upstream release log is here: https://github.com/astral-sh/ruff/releases
Owner

Metadata Update from @ngompa:

  • Issue tagged with: updates policy exception
**Metadata Update from @ngompa**: - Issue tagged with: updates policy exception
Owner

This is basically the same as #2259 and #2525, so seems reasonable to grant.

+1

This is basically the same as #2259 and #2525, so seems reasonable to grant. +1
Owner

+1

+1
Owner

+1 the rationale makes sense

+1 the rationale makes sense

+1

+1
Owner

After a week:
APPROVED (+4, 0, 0)

After a week: APPROVED (+4, 0, 0)
Owner

Metadata Update from @zbyszek:

  • Issue tagged with: document it
**Metadata Update from @zbyszek**: - Issue tagged with: document it
Owner

Announced.

Announced.
Owner

Metadata Update from @sgallagh:

  • Issue close_status updated to: Accepted
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @sgallagh**: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Owner

It still need to be documented :(

It still need to be documented :(
Owner

Metadata Update from @zbyszek:

  • Issue status updated to: Open (was: Closed)
**Metadata Update from @zbyszek**: - Issue status updated to: Open (was: Closed)
Owner
https://pagure.io/fesco/fesco-docs/pull-request/89
Owner

Done.

Done.
Owner

Metadata Update from @zbyszek:

  • Issue untagged with: document it
  • Issue close_status updated to: Accepted
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @zbyszek**: - Issue **un**tagged with: document it - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fesco/tickets#3197
No description provided.