Document technical requirements for upgrade/downgrade feasibility checks

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: 8.2.0-rc0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-09-01
    • 馃煩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      In FCV_AND_FEATURE_FLAG_README.md document the technical requirements for feasibility checks that may be added to _userCollectionsUassertsForDowngrade or _userCollectionsUassertsForUpgrade, for example:

      • Feasibility checks are expected to be fast (<10s in reasonable circumstances).
      • Feasibility checks should not scan large datasets (e.g. user data, chunks, etc.).

      Additionally note that feasibility checks during the upgrade (i.e. removed features) need to be reviewed by Server Release.

            Assignee:
            Virginia Chac贸n P茅rez (Inactive)
            Reporter:
            Joan Bruguera Mic贸
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: