https://community.esri.com/t5/arcgis-pro-ideas/make-2026-the-pro-snow-leopard-year/idi-p/1669478 <P>Please take a page from Apple's book and make 2026 a Snow Leopard Year for ArcGIS Pro.&nbsp;<BR /><BR />Apple's core concept was to create a very reliable and stable version with very few feature updates and a focus on bug fixes, speed and stability improvements for that release.&nbsp; (This Idea does not claim that Apple was or was not successful&nbsp;<span class="lia-unicode-emoji" title=":grinning_face:">😀</span> )<BR /><BR />There have been substantial issues, that I seems to be lucky enough to encounter, since early 3.x and each subsequent version fixing a bug but introducing another.&nbsp; Every couple of posts in this forum start with 'we are on 2.x/3.early and we have this problem but cannot update for reasons'.&nbsp;<BR /><BR />As the market leader by a significant margin, wouldn't it do more good to to take a breath and address the various core Pro issues and then move forward again?&nbsp;&nbsp;<BR /><BR />This base version could then form an LTS version (long term support version) that will receive proper bug fixes for an extended period of time while you have the 6-monthly feature updates for a period until the next LTS version. (This is another Idea&nbsp;<A href="https://community.esri.com/t5/arcgis-pro-ideas/change-pro-development-to-use-a-more-conservative/idi-p/1547856" target="_blank">https://community.esri.com/t5/arcgis-pro-ideas/change-pro-development-to-use-a-more-conservative/idi-p/1547856</A>&nbsp;)</P><P>As a secondary thought - in order to maintain the stated Pro roadmap - why not break Pro up into a more modular ecosystem?&nbsp; Take the year to build a more solid core with better UI, stability (as in not crash + feature stable), and more tools to troubleshoot and manage an install with, etc. (see other Ideas about profile backup &amp; audit tools, improved install/reinstall, containerised delivery, etc.).</P><P>Then focus on building 'features' as a plug-in model where the tool library is split from the core application and development can then proceed separately? A new tool can be launched that is suitable for 26.05LTS and any subsequent versions up to the next LTS version.&nbsp; Organisations can then plan more palatable core upgrade cycles yet users don't have to lose out on features that make them more efficient.</P> Mon, 01 Dec 2025 23:11:34 GMT RTPL_AU 2025-12-01T23:11:34Z https://community.esri.com/t5/arcgis-pro-ideas/make-2026-the-pro-snow-leopard-year/idi-p/1669478 <P>Please take a page from Apple's book and make 2026 a Snow Leopard Year for ArcGIS Pro.&nbsp;<BR /><BR />Apple's core concept was to create a very reliable and stable version with very few feature updates and a focus on bug fixes, speed and stability improvements for that release.&nbsp; (This Idea does not claim that Apple was or was not successful&nbsp;<span class="lia-unicode-emoji" title=":grinning_face:">😀</span> )<BR /><BR />There have been substantial issues, that I seems to be lucky enough to encounter, since early 3.x and each subsequent version fixing a bug but introducing another.&nbsp; Every couple of posts in this forum start with 'we are on 2.x/3.early and we have this problem but cannot update for reasons'.&nbsp;<BR /><BR />As the market leader by a significant margin, wouldn't it do more good to to take a breath and address the various core Pro issues and then move forward again?&nbsp;&nbsp;<BR /><BR />This base version could then form an LTS version (long term support version) that will receive proper bug fixes for an extended period of time while you have the 6-monthly feature updates for a period until the next LTS version. (This is another Idea&nbsp;<A href="https://community.esri.com/t5/arcgis-pro-ideas/change-pro-development-to-use-a-more-conservative/idi-p/1547856" target="_blank">https://community.esri.com/t5/arcgis-pro-ideas/change-pro-development-to-use-a-more-conservative/idi-p/1547856</A>&nbsp;)</P><P>As a secondary thought - in order to maintain the stated Pro roadmap - why not break Pro up into a more modular ecosystem?&nbsp; Take the year to build a more solid core with better UI, stability (as in not crash + feature stable), and more tools to troubleshoot and manage an install with, etc. (see other Ideas about profile backup &amp; audit tools, improved install/reinstall, containerised delivery, etc.).</P><P>Then focus on building 'features' as a plug-in model where the tool library is split from the core application and development can then proceed separately? A new tool can be launched that is suitable for 26.05LTS and any subsequent versions up to the next LTS version.&nbsp; Organisations can then plan more palatable core upgrade cycles yet users don't have to lose out on features that make them more efficient.</P> Mon, 01 Dec 2025 23:11:34 GMT https://community.esri.com/t5/arcgis-pro-ideas/make-2026-the-pro-snow-leopard-year/idi-p/1669478 RTPL_AU 2025-12-01T23:11:34Z https://community.esri.com/t5/arcgis-pro-ideas/make-2026-the-pro-snow-leopard-year/idc-p/1669803#M36887 <P>I absolutely agree!</P><P>I am not upgrading becasue of bugs.</P> Tue, 02 Dec 2025 18:21:23 GMT https://community.esri.com/t5/arcgis-pro-ideas/make-2026-the-pro-snow-leopard-year/idc-p/1669803#M36887 MichaelPorter2 2025-12-02T18:21:23Z