Support/TikiUpgradePlan: Difference between revisions

Summary:

The plan is to figure out a way to combine locally maintained Tiki code that we haven't upstreamed (most notably the forum, our theme, and SHOWFOR) with the latest stable version of Tiki. This involves setting up an IT infrastructure where our locally maintained code isn't affected by a Tiki svn update.

Some local modifications to the code will most likely be needed to ensure that e.g. our Tiki 1.10 forum hooks into the latest Tiki code. The idea is that we do this as early in Q1 as possible and script it, or document anything that needs manual work. The goal is to have a working copy of SUMO with the latest Tiki code combined with our local fixes (theme, forum, SHOWFOR, etc) up at http://tiki-trunk.mozilla.com/ so we can start the actual regression testing.

As we find problems on http://tiki-trunk.mozilla.com/, we will patch and '''upstream''' all fixes to Tiki trunk to ensure that we don't run into the problem in the next upgrade cycle.

Of course, in addition to upstreaming our patches, we also apply them locally. In other words, our local Tiki installation will gradually stabilize throughout the regression testing/fixing process. And since we also upstream the patches, we can be confident that once we upgrade Tiki again to the stable version 5.1, we won't have to redo any of the upstreamed fixes along the way.

At this point, Tiki 5.1 stable is released and our task is to pull down the latest Tiki code again -- keeping our local infrastructure intact using scripts or documented manual IT work -- and perform final QA.

If we still have problems, we will fix and upstream patches to Tiki trunk as usual, to ensure that we don't encounter this problem in a future Tiki 6.1 upgrade, but we won't pull down the latest source again in this upgrade cycle after this point.