Latest revision as of 00:48, 25 May 2016

Suds Jurko Fork

Summary

Change the python-suds package to use the fork maintained by Jurko Gospodnetić.

Owner

Name: Scott Talbert
Email: swt@techie.net
Release notes owner:

Current status

Targeted release: Fedora 24
Last updated: 2016-05-25
Tracker bug: #1301535

Detailed Description

Suds is a SOAP-based web service client for Python which is currently packaged in Fedora as python-suds. This change proposal aims to update the python-suds package to use the fork maintained by Jurko Gospodnetić. Currently Fedora has the original version of Suds which has not been maintained or updated since 2011. The original version does not support Python 3.

Benefit to Fedora

This change brings a more modern Suds to Fedora, including Python 3 support and various bug fixes.

Scope

Proposal owners:
- Update existing python-suds package to suds-jurko and ensure it builds/works in Rawhide. (NOTE: proposal owner is not currently the maintainer of python-suds, but would intend to assume maintainership as part of this change.) The plan is to use the latest hg snapshot of suds-jurko.
- In conjunction with the python-suds dependent package maintainers, help test dependent packages to ensure they work correctly with the new package.

Other developers:
- For maintainers of packages that depend on python-suds: test the dependent packages to ensure they work correctly with the updated python-suds package. No changes should be needed as the Jurko fork is believed to maintain compatibility with the original Suds. One exception has been noted:
  - Two debug-related functions have been removed (Client.last_sent() and Client.last_received()) but a workaround is available (upstream issue).

Release engineering: None
- List of deliverables: None

Policies and guidelines: None

Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

No impact expected.

How To Test

No special hardware or data is required. To test, one would install a python-suds dependent package and verify that it functions as it did with the previous package.

User Experience

No changes expected to user experience.

Dependencies

The packages below depend on python-suds in Rawhide. The test status will be tracked in the table below.

Package	Status
chirp
condor-aviary-common
condor-aviary-hadoop-common
congruity	Works
fence-agents-ovh
fence-agents-pve
fence-agents-vmware-soap
python-oslo-vmware
python-psphere
python-vatnumber	Works
virt-who	Works

Contingency Plan

Contingency mechanism: Revert python-suds back to the previous release.
Contingency deadline: Beta Freeze
Blocks release? No
Blocks product? No

Documentation

https://bitbucket.org/jurko/suds

Release Notes

@@ Line 27: / Line 27: @@
 CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 -->
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1301535 #1301535]
 == Detailed Description ==
-Suds is a SOAP-based web service client for Python which is currently packaged in Fedora as python-suds. This change proposal aims to update the python-suds package to use the fork maintained by Jurko Gospodnetić. Currently Fedora has the original version of Suds which has not been maintained or updated since 2011.
+Suds is a SOAP-based web service client for Python which is currently packaged in Fedora as [https://admin.fedoraproject.org/pkgdb/package/rpms/python-suds/ python-suds]. This change proposal aims to update the python-suds package to use the [https://bitbucket.org/jurko/suds fork] maintained by Jurko Gospodnetić. Currently Fedora has the [https://fedorahosted.org/suds/ original version] of Suds which has not been maintained or updated since 2011.  The original version does not support Python 3.
 == Benefit to Fedora ==
@@ Line 39: / Line 39: @@
 == Scope ==
 * Proposal owners:
-<!-- What work do the feature owners 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?-->
+** Update existing python-suds package to suds-jurko and ensure it builds/works in Rawhide.  (NOTE: proposal owner is not currently the maintainer of python-suds, but would intend to assume maintainership as part of this change.)  The plan is to use the latest hg snapshot of suds-jurko.
+** In conjunction with the python-suds dependent package maintainers, help test dependent packages to ensure they work correctly with the new package.
-* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Other developers:
-<!-- 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?-->
+** For maintainers of packages that depend on python-suds: test the dependent packages to ensure they work correctly with the updated python-suds package.  No changes should be needed as the Jurko fork is believed to maintain compatibility with the original Suds.  One exception has been noted:
+*** Two debug-related functions have been removed (Client.last_sent() and Client.last_received()) but a workaround is available ([https://bitbucket.org/jurko/suds/issues/39/missing-last_sent-and-last_received upstream issue]).
 * Release engineering: None
@@ Line 52: / Line 54: @@
 == 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? -->
+No impact expected.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == How To Test ==
-<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
+No special hardware or data is required. To test, one would install a python-suds dependent package and verify that it functions as it did with the previous package.
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
-A good "how to test" should answer these four questions:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == 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. -->
+No changes expected to user experience.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Dependencies ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
+The packages below depend on python-suds in Rawhide.  The test status will be tracked in the table below.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+{| class="wikitable"
-N/A (not a System Wide Change)
+!|Package
+!|Status
+|-
+|chirp
+|
+|-
+|condor-aviary-common
+|
+|-
+|condor-aviary-hadoop-common
+|
+|-
+|congruity
+|Works
+|-
+|fence-agents-ovh
+|
+|-
+|fence-agents-pve
+|
+|-
+|fence-agents-vmware-soap
+|
+|-
+|python-oslo-vmware
+|
+|-
+|python-psphere
+|
+|-
+|python-vatnumber
+|Works
+|-
+|virt-who
+|Works
+|}
 == Contingency Plan ==
-<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+* Contingency mechanism: Revert python-suds back to the previous release.
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency deadline: Beta Freeze
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
+* Blocks release? No
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks product? No
-<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
 == Documentation ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+https://bitbucket.org/jurko/suds
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Release Notes ==
@@ Line 109: / Line 120: @@
 -->
-[[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 -->
 <!-- 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-->
+<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangeReadyForWrangler-->
 <!-- Select proper category, default is Self Contained Change -->
 <!-- [[Category:SelfContainedChange]] -->
 [[Category:SystemWideChange]]

Search

Changes/Suds Jurko Fork: Difference between revisions