From Fedora Project Wiki
(Created page with "<!-- 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 is...")
 
No edit summary
Line 78: Line 78:
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engeneering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
* Release engineering: N/A <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->

Revision as of 14:03, 14 February 2017


Docker SDK for Python, version 2

Summary

Add new version of "Docker SDK for Python" to Fedora. This obsoletes existing python-docker-py package.

Owner

Current status

  • Targeted release: Fedora 26
  • Last updated: 2017-02-14
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

On December 2016, upstream released a new version of python library which communicates with Docker engine API. This new release is not backwards compatible with previous 1.x series. As part of this release, the upstream also renamed the package: it used to be named docker-py on PyPI, now it's named docker.

We need to start a new review process and get the latest version of the library to Fedora. Since the update will be backwards incompatible, we need to make sure that all the software requiring this library works with it.

Benefit to Fedora

docker-compose requires the newest version of the library. So in order to have the latest & greatest software from Docker Inc., we need to do this update.


Scope

  • Proposal owners:
    • Submit a review
    • Do a production build
    • Make sure that all the dependencies work with the updated package
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

This change will probably affect some users since it is backwards incompatible.

How To Test

  • Install docker-compose-1.11 and test if it works.
  • Install atomic and test if it works.

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: 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? N/A

Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/Docker_SDK_For_Python_Version_2&oldid=486111"