Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 6.0.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      PuppetDB
    • Release Notes:
      Deprecation
    • Release Notes Summary:
      Hide
      This initial draft is already in release_notes.markdown:

      [upgrade_policy]: ./versioning_policy.html#upgrades

      ## 6.0.0

      ## Upgrading

      - Support for ActiveMQ has been completely removed, meaning that PuppetDB can no longer convert an existing queue to the new format when upgrading from versions older than 4.3.0, but since PuppetDB's [upgrade policy][upgrade_policy] forbids skipping major versions, this should not present a problem since any version 5 release will perform the conversion at startup.

      As a result of the removal, these ActiveMQ specific configuration options have been retired: `store-usage`, `temp-usage`, `memory-usage`, and `max-frame-size`,
      Show
      This initial draft is already in release_notes.markdown: [upgrade_policy]: ./versioning_policy.html#upgrades ## 6.0.0 ## Upgrading - Support for ActiveMQ has been completely removed, meaning that PuppetDB can no longer convert an existing queue to the new format when upgrading from versions older than 4.3.0, but since PuppetDB's [upgrade policy][upgrade_policy] forbids skipping major versions, this should not present a problem since any version 5 release will perform the conversion at startup. As a result of the removal, these ActiveMQ specific configuration options have been retired: `store-usage`, `temp-usage`, `memory-usage`, and `max-frame-size`,
    • QA Risk Assessment:
      Needs Assessment

      Attachments

        Issue Links

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                rob.browning Rob Browning
                Reporter:
                rob.browning Rob Browning
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support