Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-1045

Check for new version

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Normal Normal
    • 2.1
    • None
    • None
    • None

      A maximum of once per week, at start-up Picard should check to see whether there is a new official version and if so inform the user (with a URL for download).

        1. checkupdate.py
          6 kB

          [PICARD-1045] Check for new version

          Philipp Wolfer made changes -
          Fix Version/s New: 2.1.0 [ 11126 ]
          Fix Version/s Original: 2.1.0dev2 [ 11113 ]
          Philipp Wolfer made changes -
          Link New: This issue is a dependency of PICARD-1325 [ PICARD-1325 ]
          Philipp Wolfer made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Release Pending [ 10006 ] New: Closed [ 6 ]
          Philipp Wolfer made changes -
          Issue Type Original: Improvement [ 4 ] New: New Feature [ 2 ]
          Philipp Wolfer made changes -
          Fix Version/s New: 2.1.0 [ 11113 ]
          Status Original: Review Submitted [ 5 ] New: Release Pending [ 10006 ]
          Philipp Wolfer made changes -
          Status Original: Open [ 1 ] New: Review Submitted [ 5 ]

          Philipp Wolfer added a comment -

          https://github.com/metabrainz/picard/pull/904

          Philipp Wolfer added a comment - https://github.com/metabrainz/picard/pull/904
          Bob Swift made changes -
          Link New: This issue depends on PW-62 [ PW-62 ]
          Bob Swift made changes -
          Assignee New: Bob Swift [ rdswift ]

          Bob Swift added a comment -

          When the PR is submitted, the code will have changed slightly from that posted in the previous comment. The version tuple comparison function will be moved to the picard/util/_init_.py file rather than the file with the UpdateCheckManager class. This is to avoid issues when trying to perform unit tests on the function because the checkupdate.py file imports picard.tagger. The comparison function will also zero out the fifth element of a test item if the version type for that item is 'final'. That came up as an issue during unit testing here. A unit test file (currently containing 52 tests of the comparison function) will also be included.

          Bob Swift added a comment - When the PR is submitted, the code will have changed slightly from that posted in the previous comment. The version tuple comparison function will be moved to the picard/util/_ init _.py file rather than the file with the UpdateCheckManager class. This is to avoid issues when trying to perform unit tests on the function because the checkupdate.py file imports picard.tagger. The comparison function will also zero out the fifth element of a test item if the version type for that item is 'final'. That came up as an issue during unit testing here. A unit test file (currently containing 52 tests of the comparison function) will also be included.

            rdswift Bob Swift
            sophist Sophist
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                2.1