Christian Boltz
1/11/2013 11:12 AM >>> Hello,
Am Donnerstag, 10. Januar 2013 schrieb Scott Weber:
We've gone through and re-upgraded the stage site to 1.19.3 and all the changes are now in the mw_upgrade_1.19 branch. The site is functioning on stage, and we have created a stage test user that can be used to test the functionality of the upgrade. If all testing goes according to plan, then we will plan on upgrading production to 1.19.3 on Monday, 01/21/2013. This gives us a week of testing.
That's good news :-) Thanks!
I had a short look at it, and it seems you accidently overwrote two commits that were only in the 1_19 branch:
https://github.com/openSUSE/wiki/commit/1a6d3e9c3adad3ef7b53bbc5e9d2bbfc4d44... add Bento print.css
https://github.com/openSUSE/wiki/commit/45b40dfacd2f9849457b9072dfa4431ea91f... add and include ReplaceText extension (not sure if this commit still has the latest version - you might just checkout the latest upstream code and include it in LocalSettings.php)
Can you please re-integrate those commits in the 1_19 branch? These changes have been reimplemented and have been re-pushed out to the mw_upgrade_1.19 branch.
Unfortunately, we will be limited to MW 1.19 as the hardware and backup process currently used does not support SLES 11 SP2 and therefore, does not support PHP 5.3+. We do have a tentative plan to fix this issue come March. So at that point we can look at potentially upgrading further to 1.20.
As I wrote, 1.19 will have long term support. This also means: If we don't need one of the new features in 1.20, we can stay with the 1.19 branch ;-)
I am more than happy to stay with 1.19 as long as we want or can. It is just really nice to know that as of March we will have the ability to move to 1.20 if we desire. Thanks Scott Weber