Skip to content

po/shadow.pot: Update pot file#1645

Closed
alejandro-colomar wants to merge 1 commit into
shadow-maint:masterfrom
alejandro-colomar:pot
Closed

po/shadow.pot: Update pot file#1645
alejandro-colomar wants to merge 1 commit into
shadow-maint:masterfrom
alejandro-colomar:pot

Conversation

@alejandro-colomar

Copy link
Copy Markdown
Collaborator

I've updated it by running 'make dist'.

Cc: @mariobl, @mlh85386

I've updated it by running 'make dist'.

Signed-off-by: Alejandro Colomar <alx@kernel.org>
@alejandro-colomar alejandro-colomar marked this pull request as draft June 14, 2026 19:33
@hallyn

hallyn commented Jun 16, 2026

Copy link
Copy Markdown
Member

I wonder whether CI should regenerate shadow.pot whenever any of the files listed in po/POTFILES.in are update.

@hallyn

hallyn commented Jun 16, 2026

Copy link
Copy Markdown
Member

Anyway, lgtm if you want to merge this.

@alejandro-colomar

Copy link
Copy Markdown
Collaborator Author

I wonder whether CI should regenerate shadow.pot whenever any of the files listed in po/POTFILES.in are update.

I don't like automated commits. I'd like to oppose that.

Maybe we can "regularly" (i.e., whenever we remember) regenerate it. Like maybe once every one or two months, when one remembers to do it.

@alejandro-colomar

alejandro-colomar commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator Author

Anyway, lgtm if you want to merge this.

I'll regenerate the other file, then open for review. Thanks!

@mariobl

mariobl commented Jun 17, 2026

Copy link
Copy Markdown

Maybe we can "regularly" (i.e., whenever we remember) regenerate it. Like maybe once every one or two months, when one remembers to do it.

Assuming that shadow will one day be available on the Translation Project, it would be sufficient to update both .pot files when a pre-release tarball is sent to the robot. In the meantime, translators can update the files on demand (maybe the instuctions for this could be reviewed and clarified).

@alejandro-colomar

Copy link
Copy Markdown
Collaborator Author

Maybe we can "regularly" (i.e., whenever we remember) regenerate it. Like maybe once every one or two months, when one remembers to do it.

Assuming that shadow will one day be available on the Translation Project, it would be sufficient to update both .pot files when a pre-release tarball is sent to the robot. In the meantime, translators can update the files on demand (maybe the instuctions for this could be reviewed and clarified).

Maybe we can release an -rc already. After all, the plan was to release on June.

We won't be able to release on June because we have some regressions that need to be fixed, but we could do an -rc already.

@hallyn , would you do an -rc?

@hallyn

hallyn commented Jun 17, 2026

Copy link
Copy Markdown
Member

Lemme see if I hit any roadblocks in making an rc right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants