|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->
| | {{delete|darktable 5.0 is not a major update}} |
| | |
| = Change Proposal Name <!-- The name of your change proposal --> =
| |
| | |
| {{Change_Proposal_Banner}} | |
| | |
| == Summary ==
| |
| darktable major upgrade from version 4.8.1 to 5.0
| |
| <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
| |
| | |
| == Owner ==
| |
| <!--
| |
| For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
| |
| This should link to your home wiki page so we know who you are.
| |
| -->
| |
| * Name: [[User:germano| Germano Massullo]]
| |
| | |
| | |
| == Current status ==
| |
| [[Category:ChangeReadyForWrangler]]
| |
| <!-- When your change proposal page is completed and ready for review and announcement -->
| |
| <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
| |
| <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
| |
| <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
| |
| | |
| [[Category:SelfContainedChange]]
| |
| | |
| * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f42/ Fedora Linux 42]
| |
| * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
| |
| <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
| |
| Bugzilla state meanings:
| |
| ASSIGNED -> accepted by FESCo with ongoing development
| |
| MODIFIED -> change is substantially done and testable
| |
| ON_QA -> change is fully code complete
| |
| -->
| |
| * [<link to devel-announce post will be added by Wrangler> Announced]
| |
| * [<will be assigned by the Wrangler> Discussion thread]
| |
| * FESCo issue: <will be assigned by the Wrangler>
| |
| * Tracker bug: <will be assigned by the Wrangler>
| |
| * Release notes tracker: <will be assigned by the Wrangler>
| |
| | |
| == Detailed Description ==
| |
| darktable major upgrade from version 4.8.1 to 5.0
| |
| Details at https://github.com/darktable-org/darktable/releases/tag/release-5.0.0
| |
| | |
| == Feedback ==
| |
| darktable 5.0 is fully working on Fedora | |
| | |
| == Benefit to Fedora ==
| |
| <!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved?
| |
|
| |
| Be sure to include the following areas if relevant:
| |
| If this is a major capability update, what has changed?
| |
| For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
| |
| If this is a new functionality, what capabilities does it bring?
| |
| For example: This change allows package upgrades to be performed automatically and rolled-back at will.
| |
| Does this improve some specific package or set of packages?
| |
| For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
| |
| Does this improve specific Spins or Editions?
| |
| For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
| |
| Does this make the distribution more efficient?
| |
| For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
| |
| Is this an improvement to maintainer processes?
| |
| For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
| |
| Is this an improvement targeted as specific contributors?
| |
| For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
| |
| | |
| When a Change has multiple benefits, it's better to list them all.
| |
| | |
| Consider these Change pages from previous editions as inspiration:
| |
| https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
| |
| https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
| |
| https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
| |
| https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
| |
| https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
| |
| -->
| |
| | |
| == Scope ==
| |
| * Proposal owners:
| |
| Change owner will update the existing darktable 4.8.1 package to 5.0
| |
| | |
| | |
| * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| No action required
| |
| | |
| * Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
| |
| <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
| |
| | |
| * Trademark approval: N/A (not needed for this Change)
| |
| <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
| |
| | |
| * Alignment with the Fedora Strategy:
| |
| <!-- Does your proposal align with the current Fedora Strategy: https://discussion.fedoraproject.org/t/fedora-strategy-2028-february-march-planning-work-and-roadmap-til-flock/43618 ? It's okay if it doesn't, but it's something to consider -->
| |
| | |
| == Upgrade/compatibility impact ==
| |
| <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
| |
| | |
| | |
| == Documentation ==
| |
| https://github.com/darktable-org/darktable/releases/tag/release-5.0.0
| |
| | |
| == Release Notes ==
| |
| https://github.com/darktable-org/darktable/releases/tag/release-5.0.0
| |
