Skip to content

Scriptize version bumpΒ #10

@rffontenelle

Description

@rffontenelle

Bumping python-doc versions in Transifex requires a lot of work, but there is a lot of resource automating this, like the public API and the Python SDK. It would be nice to have scripts automating steps (in CI whenever possible) so it requires only double-checking the result.

Macro idea

  • Merge python-docs-tx-translations with this repo, putting translations in another branch named 'translations' or 'locales'.
  • A Python script of argparse arguments that call functions. CI workflow that manually run each script argument (finish and wait for double-checking results for moving to the next steps.
  • tx pull reviewed and only-translated files into different folders, so I can first push reviewed (flag it as reviewed!) and then push translated in order for the versioned project honor the reviewed state?

Step 1: Lock all resources and update translation files

  1. Lock python-newest resources
  2. Do tx pull python-newest (duration: more than 2 hours)

Step 2: Versioned project creation

  1. Create python-XXX project (e.g python-311)
  2. Create resources for python-XXX before pushing translations (good for setting the proper name)
  3. Patch '.tx/config' from "p:python-newest" to "p:python-xxx"
  4. Do tx push sources to python-XXX (required!)
  5. Do tx push translations to python-XXX (duration: less than 30 minutes)

Step 3: Version bump of python-newest

  1. Update ci.yml with new version
  2. Manually run ci.yml to:
    1. make pot for new python-newest
    2. create python-newest resources if not existent (good for setting the proper name
    3. tx push sources (from pot)
    4. check unused resources: lock & delete procedure (frc-docs-translations style)
  3. Unlock python-newest resources, if locked (save API call when unlocked already)

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesthelp wantedExtra attention is needed

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions