Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-401

Upgrade to Liquid 4.x (Originally "no official reference for Liquid 3.x")

    XMLWordPrintable

Details

    Description

      The official Liquid reference moved to v4.x. As 3scale is using 3.x, there's no official reference for the version. So we should upgrade to Liquid 4.x.

      (shopify.github.com is the repository, but there's no appropriate branches, tags or releases.)

      Dev notes
      https://github.com/Shopify/liquid/blob/master/History.md

      We should have a round table to do something smarter and more 4.0 compatible. Liquid is not that great and we are only guessing on its possible performance increase which probably cannot save seconds.
      In general we are too much bug fixing as opposed to innovation.

      Include an upgrade guide for customers.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-4515 Liquid statement looping through large number of services introduces unacceptable page load time

          • Critical - To be worked on immediately following BLOCKER issues.
          • To Develop
          is blocked by

          Sub-task - The sub-task of the issue THREESCALE-4053 Investigation for upgrade to Liquid 4.x

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is documented by

          Task - Represents a small unit of work that is not end-user facing. THREESCALE-6079 Documentation impact of upgrading from Liquid 3.x to Liquid 4.x

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Defined
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. THREESCALE-5660 Upgrades for 2.x lifecycle Part 1

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. THREESCALE-10285 Upgrades for 2.x lifecycle Part 2

          • Critical - To be worked on immediately following BLOCKER issues.
          • To Develop

          Bug - A problem that impairs or prevents the functions of the product. THREESCALE-5213 System-app memory usage continuously grows over time

          • Critical - To be worked on immediately following BLOCKER issues.
          • To Develop

          Activity

            People

              Unassigned Unassigned
              rhn-support-tkonishi Takayuki Konishi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: