Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-13815

Drive: set up Drive update site, versioning policy

    XMLWordPrintable

    Details

    • Type: User story
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.9.4
    • Component/s: Nuxeo Drive
    • Epic Link:
    • Sprint:
      Sprint Drive (5.9.4-1)
    • Story Points:
      8

      Description

      The update site will probably be a simple Apache sever hosting at least:

      • An index of compatibility between client and server versions
      • The Drive releases

      The index could look like this:

      Drive version Nuxeo server compliant versions
      2.0 6.0
      1.3.0307 5.9.1, 5.9.2, 5.9.3
      1.3.0221 5.8.0-HF08, 5.9.1, 5.9.2, 5.9.3
      1.3.0114 5.8.0-HF08, 5.9.1, 5.9.2
      1.2.1223 5.7.2, 5.8
      1.2.1031 5.6.0-HF31, 5.7.2, 5.8
      1.0.0412 5.6
      ... ...

      This would allow the client being aware of its own version and the version of the Nuxeo server to which it is connected to know if:

      1. The client is too old for the Nuxeo server (eg: 1.1.0412 / 5.9.3)
      2. The client is too recent for the Nuxeo server (eg: 1.3.0307 / 5.8)
      3. The client is compatible with the Nuxeo server but is not the latest compatible version (eg: 1.3.0221 / 5.9.3)
      4. The client is compatible with the Nuxeo server and is the latest compatible version (eg: 1.3.0307 / 5.9.3)

      The server version and compatibility index URL will be fetched by the client by a call to a dedicated operation, see NXP-13816
      For each case the client will need to decide what to do, see NXP-13817

      The index will probably be exported as JSON.
      The update site can be hosted at http://community.nuxeo.com/static/drive/

        Attachments

          Issue Links

          depends on

          Task - A task that needs to be done. NXP-13816 Drive: add an operation to fetch server version and update site URL

          • Major - Major loss of function.
          • Resolved
          is required by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. NXP-11588 Auto update of Drive Client

          • Major - Major loss of function.
          • Resolved

          User story - Created by Jira Software - do not edit or delete. Issue type for a user story. NXP-13817 Drive: Implement a wrapper/launcher able to fetch compatibility/update information and give user feedback

          • Major - Major loss of function.
          • Resolved

          User story - Created by Jira Software - do not edit or delete. Issue type for a user story. NXP-14341 Drive: make marketplace package rely on update site to download Drive client

          • Major - Major loss of function.
          • Resolved

          User story - Created by Jira Software - do not edit or delete. Issue type for a user story. NXDRIVE-40 Drive : Update site release process by Jenkins

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          User story - Created by Jira Software - do not edit or delete. Issue type for a user story. NXDRIVE-42 Drive: write documentation about Nuxeo Drive update site

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          User story - Created by Jira Software - do not edit or delete. Issue type for a user story. NXP-14358 Drive: Handle HF in update Site

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

            Activity

              People

              • Assignee:
                ataillefer Antoine Taillefer
                Reporter:
                ataillefer Antoine Taillefer
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 week Original Estimate - 1 week
                  1w
                  Remaining:
                  Time Spent - 2 days Remaining Estimate - 1 week
                  1w
                  Logged:
                  Time Spent - 2 days Remaining Estimate - 1 week
                  2d