Details

    • Type: Wish Wish
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.3.0
    • Fix Version/s: 0.6.0
    • Component/s: contrib/python
    • Labels:
      None

      Description

      It is already difficult to maintain the Java code and since it should have completely superseded the Python functionality it should replace it. Some have reported it having issues already, so maybe we should think about dropping it? All missing functionality should be added to Whirr through specific JIRA issues.

        Activity

        Hide
        Tom White added a comment -

        +1

        We could move it to a sandbox area in svn, and no longer release it or publish documentation on it. The biggest thing lacking in the Java implementation is EBS support (although the Python implementation is out of date on this), although this has been started in WHIRR-252.

        Show
        Tom White added a comment - +1 We could move it to a sandbox area in svn, and no longer release it or publish documentation on it. The biggest thing lacking in the Java implementation is EBS support (although the Python implementation is out of date on this), although this has been started in WHIRR-252 .
        Hide
        Andrei Savu added a comment -

        +1

        Some users get confused and are unable to understand the distinction between the Python and the Java components. Some time ago I've done some work on rewriting the Whirr core using libcloud. I will give-up on that and focus my energy on the Java version because libcloud is way behind jclouds in terms of features and it seems like the development is moving forward slowly. I believe we should also archive and remove the open issues related to contrib/python from JIRA.

        Show
        Andrei Savu added a comment - +1 Some users get confused and are unable to understand the distinction between the Python and the Java components. Some time ago I've done some work on rewriting the Whirr core using libcloud. I will give-up on that and focus my energy on the Java version because libcloud is way behind jclouds in terms of features and it seems like the development is moving forward slowly. I believe we should also archive and remove the open issues related to contrib/python from JIRA.
        Hide
        Adrian Cole added a comment -

        +1 keeping track of 2 streams of feature dev takes time away from features, and is confusing. Let's keep focus on feature development and hardening.

        Show
        Adrian Cole added a comment - +1 keeping track of 2 streams of feature dev takes time away from features, and is confusing. Let's keep focus on feature development and hardening.
        Hide
        Andrei Savu added a comment -

        Do we have enough votes for a change? Can we do this in 0.5.0?

        Show
        Andrei Savu added a comment - Do we have enough votes for a change? Can we do this in 0.5.0?
        Hide
        Tom White added a comment -

        I suggest we do this for 0.6.0.

        Show
        Tom White added a comment - I suggest we do this for 0.6.0.
        Hide
        Andrei Savu added a comment -

        Tom what do you think? Can we go ahead and make this change now? I suggest we move the python contrib to a branch in the subversion repository.

        Show
        Andrei Savu added a comment - Tom what do you think? Can we go ahead and make this change now? I suggest we move the python contrib to a branch in the subversion repository.
        Hide
        Tom White added a comment -

        +1

        Here's a patch which removes the contrib docs. This should be applied and committed after creating the contrib-python branch. We also need to run "svn rm src/site/xdoc/contrib contrib".

        Show
        Tom White added a comment - +1 Here's a patch which removes the contrib docs. This should be applied and committed after creating the contrib-python branch. We also need to run "svn rm src/site/xdoc/contrib contrib".
        Hide
        Andrei Savu added a comment -

        +1 We should probably keep contrib/scripts around for a while.

        Is it possible to archive / export the JIRA issues that are related to the python contrib?

        Show
        Andrei Savu added a comment - +1 We should probably keep contrib/scripts around for a while. Is it possible to archive / export the JIRA issues that are related to the python contrib?
        Hide
        Tom White added a comment -

        > We should probably keep contrib/scripts around for a while.

        Good point, we should only remove contrib/python.

        > Is it possible to archive / export the JIRA issues that are related to the python contrib?

        We can bulk change to mark as "Won't Fix".

        Show
        Tom White added a comment - > We should probably keep contrib/scripts around for a while. Good point, we should only remove contrib/python. > Is it possible to archive / export the JIRA issues that are related to the python contrib? We can bulk change to mark as "Won't Fix".
        Hide
        Andrei Savu added a comment -

        We can bulk change to mark as "Won't Fix".

        +1

        Show
        Andrei Savu added a comment - We can bulk change to mark as "Won't Fix". +1
        Hide
        Andrei Savu added a comment -

        I've made all the changes as discussed. Thanks Tom!

        Show
        Andrei Savu added a comment - I've made all the changes as discussed. Thanks Tom!

          People

          • Assignee:
            Tom White
            Reporter:
            Lars George
          • Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development