config.changelog not integrated with locking in operations themselves

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ... resulting in changelog entries potentially being reordered in arbitrary ways over short time periods.

      It's difficult to create automated tools if we can't trust the changelog ordering - even small differences could result in failure. We can try to make our tools "guess", but this is A) hard to do in a portable way and B) won't ever be 100% correct.

            Assignee:
            [DO NOT USE] Backlog - Sharding Team
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: