# GIT - best practice **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [April 22, 2022, 9:18am UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732 "2022-04-22T09:18:08Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\ **Post date:** [April 22, 2022, 9:18am UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/1 "2022-04-22T09:18:08Z")
Hi all, We are using git to maintain a product running on the Ignition platform. After a fetch Ignition tend to play hard and cause errors to happen. The user often need to restart both servers (redundancy, yes) to get things working again. Is there a way to prevent this? - Open the designer and save after the fetch? - Open it before and refresh the project? > git fetch > git tag > git reset --hard v1.2.3 ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 22, 2022, 12:00pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/2 "2022-04-22T12:00:03Z")
Ignition v7.9 is utterly unable to play nice with version control. Upgrade to v8.1. ---
**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\ **Post date:** [April 22, 2022, 12:11pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/3 "2022-04-22T12:11:47Z")
What if upgrading is not an option? ---
**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\ **Post date:** [April 22, 2022, 12:12pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/4 "2022-04-22T12:12:35Z")
Edit, sorry. It’s 8.0.17 they are running. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 22, 2022, 12:16pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/5 "2022-04-22T12:16:33Z")
Sorry, it looks like a bug. 8.0.x is end of life and will not be getting any bug fixes. Upgrading is the only option. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 22, 2022, 12:20pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/6 "2022-04-22T12:20:41Z")
Consider revisiting the decision process that resulted in y’all trying to “maintain a product” on a version of Ignition that was known from the outset to _ **NOT** _ be a long-term-support version. 🤔 ---
**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\ **Post date:** [April 22, 2022, 12:33pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/7 "2022-04-22T12:33:36Z")
@SBL_MC What @pturmel is referencing is that only the odd numbered versions are supported long term by Ignition so 7.9, 8.1, next will be 8.3 etc. I did not know this until very recently tbch when a coworker told me informed me of this. I’m sure it’s somewhere on their site though. ---
**Author:** ![SBL\_MC](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbl_mc/32/56813_2.png) [@SBL\_MC](https://forum.inductiveautomation.com/u/SBL_MC)\ **Post date:** [April 22, 2022, 12:49pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/8 "2022-04-22T12:49:16Z")
I was not aware of this policy. 🧐 The reason we stay put at 8.0.17 is that these systems does not have basic care. The newest and future systems is bought as and could be upgraded to 8.1 at no cost. I’m aware that running older versions is not the optimal solution. Our git repository is built as a 8.0 project and cannot be fetched on to a 8.1 server without errors. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 22, 2022, 2:32pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/9 "2022-04-22T14:32:37Z")
This graphic from 2019 shows the expected support lifetime of v8.0. (Very short. I don't recall the source article for that image, but it was widely discussed on this forum.) > [@Release Timeline / End of Life Planning](https://forum.inductiveautomation.com/t/release-timeline-end-of-life-planning/23970/3): > > Is 8.1 tentatively planned for January 2020? This blog post from last year explains the extension of v7.9's active support phase to this June due to the length of time between v7.9's release and v8.1: > **[The Future of Ignition 7.9 LTS and EOL Plans](https://inductiveautomation.com/blog/the-future-of-ignition-79-lts-and-eol-plans)** > > Ignition 7.9 is the last Long-Term Support (LTS) release for the Ignition 7 branch. LTS versions of Ignition receive active support from our development and tech support teams, including improvements and fixes for a full five years after their... A similar effect will happen when v8.2 comes out. It will be glorious--new features galore, enabled by architecture changes that would be too disruptive to introduce in v8.1. But the glorious will be accompanied by the less wondrous--bugs, bumpy upgrades, and a very short support lifespan. Anyone who deploys 8.2 without Basic Care to tide you over until v8.3 (LTS again), or fails to upgrade v8.2 to v8.3 as soon as practical, is simply playing with fire. IA could emphasize this more when in the middle of a non-LTS release, but that is hard to do amidst the marketing hype and new feature excitement. A buzz-kill indeed. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [April 22, 2022, 2:43pm UTC](https://forum.inductiveautomation.com/t/git-best-practice/58732/10 "2022-04-22T14:43:49Z")
Do you have an examples of the kinds of errors you encounter and/or concrete descriptions of what actually goes wrong?