Uploaded image for project: 'SEBA'
  1. SEBA
  2. SEBA-416

Services should keep a history of xproto evolution

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Resolved (View Workflow)
    • Priority: Medium
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: February
    • Component/s: NEM
    • Labels:
      None

      Description

      See database migration document https://docs.google.com/document/d/13gGv0KuFTZuj8wa2fF8Bw73NiL0OgTt0DTkbdKGipHc,

      Allow service xproto to be specified as several versions,

      • Base
      • 1
      • 2
      • ...
      • N-1
      • N

      History will be maintained as a series of complete xproto files each of which supersedes the previous one. It's expected that only the most recent xproto file will need to be sent to the core (along with a set of data migration scripts, to be described in a separate ticket).

      It's not expected that any changes to xproto syntax are required.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            scottb Scott Baker
            Reporter:
            scottb Scott Baker
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes