[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-05 UTC。"],[],[],null,["# Standard extended support release program overview\n\n| **Note:** The information on this page applies only to Looker (original) instances. For an overview of release processes for Looker (Google Cloud core), see the [Looker (Google Cloud core) release overview](/looker/docs/looker-core-release-process) documentation page.\n\nThe ESR program has a slower deployment cycle than the standard release program and a longer total window of support. Customers on the ESR release cycle will receive new features later and less frequently and will need to update only 4 times a year (instead of 11).\n\nThe ESR program is designed for customers who prefer, or need, a more gradual pace of deployment. Every three months there will be an extended support release, which will receive three months of support following its declaration as a stable release.\n\nEach ESR version gets three months of engineering attention. When relevant and feasible, issues will be patched back to the currently supported ESR release.\n\nStaging requirements\n--------------------\n\nParticipants in the ESR program are required to pair production instances with staging instances. During the staging period for an ESR release, you will need to test the release on a staging server. During this time, you can keep an eye on the new features, the workflow changes, and any product issues that could have an impact on how you use Looker. [Google Cloud Support](https://cloud.google.com/support) is available during this staging period to assist with issue remediation, as appropriate.\n\nIs the ESR program right for you?\n---------------------------------\n\nThe ESR program was designed to serve businesses with less flexible software update policies. Consider the following questions when deciding if the ESR program is the right choice for your Looker instance.\n\n**Is your Looker instance frequently on an unsupported release?**\n\nThe ESR program can provide a path to to getting your Looker instance on a supported release consistently if it has been frequently on an [unsupported release](/looker/docs/officially-supported-releases). If the instance is usually up to date, consider continuing with the current update cycle to ensure that your Looker instance is getting new features in a timely and frequent fashion.\n\n**How do you want to receive new features?**\n\nIf you are unable to dedicate time to, or otherwise want to avoid dealing with, frequent small changes --- or if your company has long internal software update review processes --- the ESR program may be right for you.\n\n**Are you comfortable with the trade-offs between stability and non-urgent issues?**\n\nLooker anticipates that each release will be stable; however, in the software world, unexpected things can occur, especially when the platform is used in novel ways. The ESR release program will limit the chances of such an occurrence, but it may not reduce your exposure to non-urgent bugs.\n\n### Costs and benefits of each release program\n\nOpting in to the ESR program\n----------------------------\n\nIf the ESR program seems best suited for your company's business needs, reach out to [Google Cloud Support](https://cloud.google.com/support) or to your dedicated account team to discuss opting in to this program.\n\nQuestions?\n----------\n\nIf you have questions, a great place to ask them is Looker's [Community forum](https://discourse.looker.com/), where discussion of all sorts is welcomed and encouraged, including (but not limited to) Looker, business intelligence, and data in general, with other Good Lookers (customers) and Looker analysts."]]
