|
|
| Line 1: |
Line 1: |
| {{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
| |
|
| |
| <!-- Self Contained or System Wide Change Proposal?
| |
| Use this guide to determine to which category your proposed change belongs to.
| |
|
| |
| Self Contained Changes are:
| |
| * changes to isolated/leaf package without the impact on other packages/rest of the distribution
| |
| * limited scope changes without the impact on other packages/rest of the distribution
| |
| * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
| |
|
| |
| System Wide Changes are:
| |
| * changes that does not fit Self Contained Changes category touching
| |
| * changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
| |
| * changing system defaults
| |
|
| |
| For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
| |
| improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies).
| |
|
| |
| We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
| |
| -->
| |
|
| |
| <!-- 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 -->
| |
|
| |
| <!-- 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 -->
| |
| = Darktable 2.0 <!-- The name of your change proposal --> = | | = Darktable 2.0 <!-- The name of your change proposal --> = |
|
| |
|
| == Summary == | | == Summary == |
| <!-- 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. -->
| |
| Update Darktable to new 2.0 major release | | Update Darktable to new 2.0 major release |
|
| |
|
Revision as of 16:08, 12 November 2015
Darktable 2.0
Summary
Update Darktable to new 2.0 major release
Owner
- Email: <your email address so we can contact you, invite you to meetings, etc.>
- Release notes owner:
Current status
Detailed Description
Darktable is one of the most important photo editing in the whole FOSS world. The 2.0 final version is going to be released in a few weeks, and it will be shipped in Fedora 24
Benefit to Fedora
Darktable 2.0's improved support for newer cameras stresses that the FOSS world is a concrete alternative for professional (and not) photographers
Scope
- Proposal owners: actually update Darktable package to 2.0 sources.
- Other developers: nothing
- Release engineering: no action required
- Policies and guidelines: no new policy/guideline changes required.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Upgrade tested. Downgrade from 2.0 to 1.6.x not supported.
How To Test
x86 64bit CPU only.
You are expected to successfully open and edit photos already edited in Darktable 1.6.x
User Experience
N/A (not a System Wide Change)
Dependencies
The same of Darktable 1.6.x, except for gtk2* that has been replaced with gtk3*
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
https://github.com/darktable-org/darktable/releases/tag/release-2.0rc1
Release Notes
