[opensuse-web] Wiki update - status?
Hello, I didn't hear anything about the wiki upgrade since months. Can you please give a status update? ;-) To make things more interesting, - the mw_upgrade_1.19 branch on github seems to contain 1.17 again :-/ The history looks like 1.19 was never there, but I don't know git good enough to really know or find out what happened. - in the meantime, MediaWiki 1.20.2 was released (requires PHP >= 5.3.2, but en.o.o has only 5.2.14 according to special:version) - OTOH, the MediaWiki 1.19 branch will get "longterm support" [1] So, the questions are: - what happened to the mw_upgrade_1.19 branch on github? - which version will we upgrade to - 1.19 or 1.20? - is it possible to get a newer PHP on the server? (if not, this answers the previous question ;-) - can you give a timeframe for the upgrade? As a wild idea, I was also thinking about switching to OpenID login. The advantage would be that we can probably use an existing extension from upstream MediaWiki instead of having to maintain the AccessManager extension ourself. As I said, this is a wild idea - I don't know if it really makes sense or if it would work at all ;-) Regards, Christian Boltz [1] from the MediaWiki 1.20 announcement mail: | === Long Term Support === | | We're working closely with Linux distributors to make sure that the | MediaWiki bundled in Linux is something that we feel more comfortable | supporting. In this vein, MediaWiki 1.19 is being targeted for "long | term support". Since Debian (the Linux distribution with the longest | release cycle) has a two year cycle between each freeze and we've | gotten MediaWiki 1.19 into Wheezy, we'll support MW 1.19 for the next | two years. (Thank you especially to MediaWiki developer Platonides | for his help in working with the Debian developers.) --
Hier hab ich gerade noch was gefunden, was ist denn bitte ein Dialerzwang? Ein guter Grund zu einem anderen Provider zu wechseln. [> Eric Scheen und Arvin Schnell in suse-linux]
-- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Christian Boltz <opensuse@cboltz.de> 1/9/2013 9:58 AM >>> Hello,
I didn't hear anything about the wiki upgrade since months. Can you please give a status update? ;-)
To make things more interesting, - the mw_upgrade_1.19 branch on github seems to contain 1.17 again :-/ The history looks like 1.19 was never there, but I don't know git good enough to really know or find out what happened. - in the meantime, MediaWiki 1.20.2 was released (requires PHP >= 5.3.2, but en.o.o has only 5.2.14 according to special:version) - OTOH, the MediaWiki 1.19 branch will get "longterm support" [1]
So, the questions are: - what happened to the mw_upgrade_1.19 branch on github? - which version will we upgrade to - 1.19 or 1.20? - is it possible to get a newer PHP on the server? (if not, this answers the previous question ;-) - can you give a timeframe for the upgrade?
Scott is working on a reply, so I'll let him answer those questions.
As a wild idea, I was also thinking about switching to OpenID login. The advantage would be that we can probably use an existing extension from upstream MediaWiki instead of having to maintain the AccessManager extension ourself. As I said, this is a wild idea - I don't know if it really makes sense or if it would work at all ;-)
Novell and SUSE both have OpenID providers that are integrated with the Access Manager login, so at first glance, it seems feasible. It's hard to tell without know what's currently out there. It does have the advantage of allowing people to log in with other providers that we would trust, so that's a big plus. The big disadvantage is losing the seamless login across the wikis. You would still be SSO, but you would have to click login in each wiki you visit to make it go through the authentication process. I don't think maintenance will be much of an issue either way, since we only really need to maintain it when MW makes a change to the authentication hooks. -Matt
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. 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. If you have any further questions please let me know. Thanks Scott Weber
Christian Boltz <opensuse@cboltz.de> 1/9/2013 9:58 AM >>> Hello,
I didn't hear anything about the wiki upgrade since months. Can you please give a status update? ;-) To make things more interesting, - the mw_upgrade_1.19 branch on github seems to contain 1.17 again :-/ The history looks like 1.19 was never there, but I don't know git good enough to really know or find out what happened. - in the meantime, MediaWiki 1.20.2 was released (requires PHP >= 5.3.2, but en.o.o has only 5.2.14 according to special:version) - OTOH, the MediaWiki 1.19 branch will get "longterm support" [1] So, the questions are: - what happened to the mw_upgrade_1.19 branch on github? - which version will we upgrade to - 1.19 or 1.20? - is it possible to get a newer PHP on the server? (if not, this answers the previous question ;-) - can you give a timeframe for the upgrade? As a wild idea, I was also thinking about switching to OpenID login. The advantage would be that we can probably use an existing extension from upstream MediaWiki instead of having to maintain the AccessManager extension ourself. As I said, this is a wild idea - I don't know if it really makes sense or if it would work at all ;-) Regards, Christian Boltz [1] from the MediaWiki 1.20 announcement mail: | === Long Term Support === | | We're working closely with Linux distributors to make sure that the | MediaWiki bundled in Linux is something that we feel more comfortable | supporting. In this vein, MediaWiki 1.19 is being targeted for "long | term support". Since Debian (the Linux distribution with the longest | release cycle) has a two year cycle between each freeze and we've | gotten MediaWiki 1.19 into Wheezy, we'll support MW 1.19 for the next | two years. (Thank you especially to MediaWiki developer Platonides | for his help in working with the Debian developers.) --
Hier hab ich gerade noch was gefunden, was ist denn bitte ein Dialerzwang? Ein guter Grund zu einem anderen Provider zu wechseln. [> Eric Scheen und Arvin Schnell in suse-linux]
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?
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 ;-) Regards, Christian Boltz -- Frag nicht nach dem Tuning des Heckspoilers wenn Du eh in einer Tempo-30-Zone bist. [Peer Heinlein in postfixbuch-users] -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Christian Boltz <opensuse@cboltz.de> 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
Hello, Am Freitag, 11. Januar 2013 schrieb Scott Weber:
Christian Boltz <opensuse@cboltz.de> 1/11/2013 11:12 AM >>> 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.
Hmmm... - looks like you didn't put a reminder in your calendar - en.o.o is still running 1.17 ;-) You might have noticed that I pushed a small change to integrate print.css also in the bentofluid theme (not sure if you deployed it to enstage already). Unfortunately I can't test it at the moment - enstage.o.o says (Can't contact the database server: Access denied for user 'wikistage'@'novprvlin0294.provo.novell.com' (using password: YES) (milo.provo.novell.com:3307)) Assuming this is just a temporary problem, and not seeing any serious bugreports about enstage.o.o - can you please check that my change didn't break anything and then upgrade the production wikis? Note: Please keep the 12.3 release schedule in mind (the release is planned for Mar 13), which means: do the upgrade now or wait until some days after the release. Regards, Christian Boltz -- Frederic, Welcome back. I hope that your inbox did not undo the therapeutic benefits of your holiday. [Larry Finger in opensuse-factory] -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Am Freitag, 11. Januar 2013 schrieb Scott Weber:
Christian Boltz <opensuse@cboltz.de> 1/11/2013 11:12 AM >>> 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.
Hmmm... - looks like you didn't put a reminder in your calendar - en.o.o is still running 1.17 ;-)
You might have noticed that I pushed a small change to integrate print.css also in the bentofluid theme (not sure if you deployed it to enstage already).
Unfortunately I can't test it at the moment - enstage.o.o says
(Can't contact the database server: Access denied for user 'wikistage'@'novprvlin0294.provo.novell.com' (using password: YES) (milo.provo.novell.com:3307))
Assuming this is just a temporary problem, and not seeing any serious bugreports about enstage.o.o - can you please check that my change didn't break anything and then upgrade the production wikis?
On Monday, we lost the entire stage database server. Two drives went out at the same time. We are working with the DBAs on a new stage database. In the case of the openSUSE wikis, we'll probably just copy down the production data, so we will have nice new data to work with in stage.
Note: Please keep the 12.3 release schedule in mind (the release is planned for Mar 13), which means: do the upgrade now or wait until some days after the release.
Due to the above, we will probably wait until the release is out. Thank you, Matt
participants (3)
-
Christian Boltz -
Matthew Ehle -
Scott Weber