Project

General

Profile

Task #1488

Pootle layout automated prepration to repository-ready files

Added by Florian Effenberger about 2 years ago. Updated 3 days ago.

Status:
Closed
Priority:
Normal
Target version:
Team - Q4/2017
Start date:
Due date:
% Done:

0%

Estimated time:

Description

The scope of this ticket is to provide Pootle layout automated prepration to repository-ready files.


Related issues

Related to Infrastructure - Task #2012: Automate pootle to commit translations Feedback

History

#1 Updated by Florian Effenberger almost 2 years ago

  • Target version changed from Q4/2015 to Q1/2016

#2 Updated by Florian Effenberger almost 2 years ago

Cloph, you asked for adding this one - is this still recent and if so, what's the status?

#3 Updated by Florian Effenberger almost 2 years ago

  • Target version changed from Q1/2016 to Q2/2016

#4 Updated by Florian Effenberger over 1 year ago

  • Priority changed from Normal to Low
  • Target version changed from Q2/2016 to Q3/2016

Talked to Cloph
This is still recent, but low-prio, so shifting to Q3

#5 Updated by Florian Effenberger over 1 year ago

  • % Done changed from 0 to 80

Done, just needs adding into Salt, then closing this ticket

#6 Updated by Florian Effenberger over 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 80 to 90

#7 Updated by Florian Effenberger about 1 year ago

Florian Effenberger wrote:

Done, just needs adding into Salt, then closing this ticket

Any updates on this?

#8 Updated by Florian Effenberger about 1 year ago

Ping?

#9 Updated by Christian Lohmaier about 1 year ago

this is speerheaded by Jan, and from my understanding the scripting framework is ready, there's an account for the commits that has been verified.

Depending on whether new version of pootle changes the exported files or not, we can enable it after migrating pootle.

#10 Updated by Florian Effenberger 11 months ago

  • Target version changed from Q3/2016 to Q1/2017

#11 Updated by Florian Effenberger 10 months ago

Christian Lohmaier wrote:

this is speerheaded by Jan, and from my understanding the scripting framework is ready, there's an account for the commits that has been verified.

Depending on whether new version of pootle changes the exported files or not, we can enable it after migrating pootle.

Any updates on that?

#12 Updated by Florian Effenberger 8 months ago

  • Target version changed from Q1/2017 to Q2/2017

#13 Updated by Florian Effenberger 5 months ago

  • Status changed from In Progress to Feedback
  • Priority changed from Low to Normal
  • Target version changed from Q2/2017 to Q3/2017
  • % Done changed from 90 to 0

IMHO the plan is to wait for back-migration of Pootle to our own infra (Guilhem currently searching for suitable bare-metal hardware) before deploying the existing deliverable - Cloph, can you confirm?

#14 Updated by Florian Effenberger 5 months ago

Florian Effenberger wrote:

IMHO the plan is to wait for back-migration of Pootle to our own infra (Guilhem currently searching for suitable bare-metal hardware) before deploying the existing deliverable - Cloph, can you confirm?

Or am I mixing up with #2012 and this one (#1488) can be closed?

#15 Updated by Christian Lohmaier 4 months ago

this is still open, but of course now additional gettext migration got "into the way" (but re scripts should not matter, the problem with that is that pootle master is not reflecting master in LO source, but still 5.4) Still pending, still planned, and still open.
And yeah, plan was to wait until moving back to our infra.

#16 Updated by Christian Lohmaier 3 months ago

  • Related to Task #2012: Automate pootle to commit translations added

#17 Updated by Florian Effenberger 3 months ago

  • Target version changed from Q3/2017 to Q4/2017

Looks like Q4 then, so shifting

#18 Updated by Christian Lohmaier 3 days ago

  • Status changed from Feedback to Closed

don't see need for keeping this one, ticket#2012 covers this → closing.

Also available in: Atom PDF