Latest revision as of 20:02, 22 April 2016

Darktable 2.0

Summary

Update Darktable to new 2.0 major release

Owner

Name: Madko
Name: Germano Massullo

Release notes owner: Simon Clark (sclark)

Current status

Targeted release: Fedora 24
Last updated: 2016-04-22
Tracker bug: #1281478

Detailed Description

Darktable is one of the most important photo editing software 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

Changelog: https://github.com/darktable-org/darktable/releases/tag/release-2.0.0

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.

Actually you can test the final release by enabling the COPR repo https://copr.fedoraproject.org/coprs/germano/Darktable_2.0_release_candidate/

You can check the .spec file at https://fedorapeople.org/~germano/darktable.spec

User Experience

N/A (not a System Wide Change)

Dependencies

The same of Darktable 1.6.x, plus colord-gtk, cups, osmgpsmap, pugixml, and gtk3* that replaced gtk2*

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

Release Notes

https://github.com/darktable-org/darktable/releases/tag/release-2.0.0

@@ 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.'''}}
+= Darktable 2.0 <!-- The name of 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 -->
-= Change Proposal Name <!-- The name of your change proposal --> =
 == 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
@@ Line 38: / Line 13: @@
 <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
-* Email: <your email address so we can contact you, invite you to meetings, etc.>
+* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->[mailto:sclark@fedoraproject.org Simon Clark] ([[User:sclark|sclark]])
-* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
 * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
@@ Line 64: / Line 38: @@
 <!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
-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
+Darktable is one of the most important photo editing software 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
+Changelog: https://github.com/darktable-org/darktable/releases/tag/release-2.0.0
 == Benefit to Fedora ==
@@ Line 88: / Line 64: @@
 x86 64bit CPU only.
-You are expected to successfully open and edit photos already edited in Darktable 1.6.x
+You are expected to successfully open and edit photos already edited in Darktable 1.6.x.
+Actually you can test the '''final''' release by enabling the COPR repo https://copr.fedoraproject.org/coprs/germano/Darktable_2.0_release_candidate/
+You can check the .spec file at https://fedorapeople.org/~germano/darktable.spec
 == User Experience ==
 <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
@@ Line 96: / Line 76: @@
 == Dependencies ==
-The same of Darktable 1.6.x, except for gtk2* that has been replaced with gtk3*
+The same of Darktable 1.6.x, plus colord-gtk, cups, osmgpsmap, pugixml, and gtk3* that replaced gtk2*
 == Contingency Plan ==
@@ Line 109: / Line 89: @@
 == Documentation ==
-https://github.com/darktable-org/darktable/releases/tag/release-2.0rc1
 == Release Notes ==
+https://github.com/darktable-org/darktable/releases/tag/release-2.0.0
 <!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
+https://github.com/darktable-org/darktable/releases/tag/release-2.0.0
 Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 -->
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF24]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 126: / Line 107: @@
 <!-- Select proper category, default is Self Contained Change -->
 <!--[[Category:SelfContainedChange]] -->
-[[Category:ChangePageIncomplete]]
+[[Category:SelfContainedChange]]

Search

Changes/Darktable 2 0: Difference between revisions