Gesendet: Montag, 12. Juni 2017 um 18:01 Uhr Von: "Sarah Julia Kriesch"
An: "Stanislav Brabec" Betreff: Aw: Re: [opensuse-translation] Weblate upgrade planned (several days outage expected) I can see different options: 1) You can do the migration during the working week. Most translotors are working then and want to translate during the weekend. 2) We wait for the release day of Leap. If Stanislav wants to use a special version of Weblate, he can download it now. Generally open source projects have got a download page with a list with all released (old) versions. He can use it, too. I Another question about the migration migration process: What is the reason for the change from mysql to postgresql? That will be a difficult change. Postgres isn't the same and I was allowed to repair such a database in the last year. I believe, you will have such problems during the migration, too.
But "Thank you for the upgrade in the future! The change management process sounds really good."
Best regards, Sarah
Gesendet: Montag, 12. Juni 2017 um 17:36 Uhr Von: "Stanislav Brabec"
An: "Ludwig Nussel" , opensuse-translation@opensuse.org Betreff: Re: [opensuse-translation] Weblate upgrade planned (several days outage expected) Ludwig Nussel wrote:
Stanislav Brabec schrieb:
We finally solved problems that were blocking our Weblate server from upgrade. We do not need to stick at the old Weblate 2.6 any more.
The bad news is the fact, that the upgrade and migration process will take a non-trivial amount of machine time (about two days) to proceed.
Thanks for the heads up! Given that we are six weeks from the release there is very little room for failures of the new version. We're also about to deploy software.o.o and I expect people to notice lots of missing translations there as the last call to action didn't yield much. I'm very much looking forward to a new version myself but I'm a bit nervous to spoil the release fun :-) Do we need anything urgent or could the migration be deferred to August, so after the release of 42.3?
The risk of migration itself is zero. The old instance would not be altered at all. The whole migration will be performed on an offline backup instance. After completing of the migration process, new server and new database will be used. If anything will fail, it is easy to switch back.
You can preview new weblate versions on https://hosted.weblate.org/
The turning the old Weblate down has the only one purpose: Perform migration on an up-to-date data set.
Testing and fixing of the migration process took a long time. Skipping many versions and two years of development is far from being trivial. Longer waiting will complicate the migration even more.
Even now, weblate released a newer version 2.14.1. But the migration was tuned and tested for 2.13.1, so we will do it for 2.13.1 and migrate to the latest version afterwards. Migration from 2.6 to any recent version could require different hacks, but migration from 2.13.1 to the next version should be seamless.
If anything will fail, it is easily possible to switch to Weblate 2.6 (one line in the opensuse.org routing tables).
We can tune up the new instance for a few days in a "Testing period", where users will be discouraged to perform big changes (comments, suggestions etc.). If any serious problem will be found, we can revert. If not, stay at the new version.
-- Best Regards / S pozdravem,
Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.com Křižíkova 148/34 (Corso IIa) tel: +49 911 7405384547 186 00 Praha 8-Karlín fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org