772896 - Update Verbatim to Pootle 2.5.0

Status: RESOLVED FIXED

(Webtools Graveyard :: Verbatim, defect)

Description

[Axel Hecht [:Pike]]

There's a new release coming up for pootle, let's find out how to get that deployed to run verbatim.

Comment 1

[Peter Bengtsson [:peterbe]]

Hi Dwayne,

To answer your questions; I guess I would be a helping hand in deploying the new Pootle. Maybe not exactly my hands but I would be able to get the right IT people to do. Also, I have sudo access on the machine if need be. 

Despite being partially in WebDev and partially in L10n here at Mozilla and maintaining several sites now, none of them actually use Verbatim. So, I actually don't know much about Pootle itself or its features. Thus I might not be good at checking the new features because I don't even know what the old ones were like :)

However, I take responsibility in rounding up the relevant people who actually have projects on Verbatim. So can Stas, Gandalf and Axel. 

In terms of deployment, what we did was that we scooped up the whole installed instance and placed it in a git repo.
https://github.com/mozilla/verbatim
Would it be an option that you submit pull requests against that as a way of doing the upgrade? I wouldn't be surprised if there are a bunch of other ad hoc commands we'll also need but perhaps that could be a good start. 

In terms of timing... Today is my last day. 
...before going on vacation for a week. So, there's little I can help with till week after next :)

I hope it helps.

Comment 2

[Dwayne Bailey]

(In reply to Peter Bengtsson [:peterbe] from comment #1)
> Hi Dwayne,
> 
> To answer your questions; I guess I would be a helping hand in deploying the
> new Pootle. Maybe not exactly my hands but I would be able to get the right
> IT people to do. Also, I have sudo access on the machine if need be. 

Great.
 
> Despite being partially in WebDev and partially in L10n here at Mozilla and
> maintaining several sites now, none of them actually use Verbatim. So, I
> actually don't know much about Pootle itself or its features. Thus I might
> not be good at checking the new features because I don't even know what the
> old ones were like :)

We can make a plan as needed around those then I think.  I'd like to be able to close out the Mozilla bugs that we are working against.

> However, I take responsibility in rounding up the relevant people who
> actually have projects on Verbatim. So can Stas, Gandalf and Axel. 

Good.
 
> In terms of deployment, what we did was that we scooped up the whole
> installed instance and placed it in a git repo.
> https://github.com/mozilla/verbatim
> Would it be an option that you submit pull requests against that as a way of
> doing the upgrade? I wouldn't be surprised if there are a bunch of other ad
> hoc commands we'll also need but perhaps that could be a good start. 

Not sure what works best in this situation.  Friedel and Julen will really be running with that, not me.  Biggest concern would be schema migrations.  So we probably at least want to test that on the current data in Verbatim to make sure that we can migrate correctly.

> In terms of timing... Today is my last day. 
> ...before going on vacation for a week. So, there's little I can help with
> till week after next :)

That's OK, as a first step we should be looking at what is different between Verbatim and Pootle trunk.

Glad your here to help.

Comment 3

[Kadir Topal [:atopal]]

Hi Dwayne, can you give an update on the status of the deployment?

Comment 4

[Kadir Topal [:atopal]]

Hi Dwayne, can you give an update on the status of the deployment?

Comment 5

[Julen Ruiz Aizpuru]

I think the ball's in Mozilla's court.

As Peter Bengtsson mentioned by mail, Mozilla needs to move Verbatim's DB to a better and more secure environment. A test DB upgrade and test deployment need to be done too.

In terms of Pootle, although the new version hasn't been released yet, bugs are being fixed and there's an ongoing work in polishing the product.
As a side note, current git master is being used at several deployments such as http://mozilla.locamotion.org/ and https://translations.documentfoundation.org/

Comment 6

[Kadir Topal [:atopal]]

Thanks for the clarification, Julen.

Peter, could you give us an update on what the status of this is?

Comment 7

[Kadir Topal [:atopal]]

Thanks for the clarification, Julen.

Peter, could you give us an update on what the status of this is?

Comment 8

[Peter Bengtsson [:peterbe]]

Finally things are getting clear. Now I know that it's up to me to set up the servers. 

So, I've blown some fresh wind into this:
https://bugzilla.mozilla.org/show_bug.cgi?id=780217

Once I know that the mysql database is in safe hands. I can set up a staging environment (see this as a test environment) where we can try doing the upgrade without affecting the production instance. 

Right now, I'm going to wait till the mysql stuff is done before I set up DNS and configure a second pootle instance running.

Comment 9

[Axel Hecht [:Pike]]

Note, the 2.5 tracker for pootle is http://bugs.locamotion.org/show_bug.cgi?id=2191

Comment 10

[Rimas Kudelis [use needinfo to ping]]

Any news regarding this? The old version of Pootle looks and feels really outdatad, especially knowing what 2.5 has to offer...

Comment 11

[Axel Hecht [:Pike]]

https://localize.mozilla.org/about/ indicates that this is FIXED for a while.