Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(1557)

Issue 6195060: CG: add updating of lilypond.pot in the release process

Can't Edit
Can't Publish+Mail
Start Review
Created:
11 years, 10 months ago by Jean-Charles
Modified:
11 years, 10 months ago
Reviewers:
Graham Percival
CC:
lilypond-devel_gnu.org
Base URL:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git/trunk/
Visibility:
Public.

Description

CG: add updating of lilypond.pot in the release process

Patch Set 1 #

Total comments: 4

Patch Set 2 : new patch #

Unified diffs Side-by-side diffs Delta from patch set Stats (+11 lines, -2 lines) Patch
M Documentation/contributor/release-work.itexi View 1 4 chunks +11 lines, -2 lines 0 comments Download

Messages

Total messages: 3
Jean-Charles
Both when releasing a stable or unstable version.
11 years, 10 months ago (2012-05-08 17:18:27 UTC) #1
Graham Percival
http://codereview.appspot.com/6195060/diff/1/Documentation/contributor/release-work.itexi File Documentation/contributor/release-work.itexi (right): http://codereview.appspot.com/6195060/diff/1/Documentation/contributor/release-work.itexi#newcode87 Documentation/contributor/release-work.itexi:87: make po-replace Thanks, this is exactly the kind of ...
11 years, 10 months ago (2012-05-10 13:26:29 UTC) #2
Jean-Charles
11 years, 10 months ago (2012-05-10 17:21:02 UTC) #3
Uploading new version

http://codereview.appspot.com/6195060/diff/1/Documentation/contributor/releas...
File Documentation/contributor/release-work.itexi (right):

http://codereview.appspot.com/6195060/diff/1/Documentation/contributor/releas...
Documentation/contributor/release-work.itexi:87: make po-replace
On 2012/05/10 13:26:29, Graham Percival wrote:
> Thanks, this is exactly the kind of thing I wanted you to do!
> 
> However, a few note: the po-replace must happen before the vi command,
otherwise
> the "make po-replace" text will be sent to the vi command when I copy&paste
the
> entire block.
> 
> Also, how about moving po-replace above the vi, then adding the git commit ...
> po/lilypond.pot above the vi command as well?  That'll make the copy&paste
> process easier.

Done.

http://codereview.appspot.com/6195060/diff/1/Documentation/contributor/releas...
Documentation/contributor/release-work.itexi:373:
coordinator@@translationproject.org, mentioning lilypond-VERSION.pot
On 2012/05/10 13:26:29, Graham Percival wrote:
> I think you already know this, but just to confirm: you know that this isn't
> part of the regular release process?

Yes, but it is not bad to give the correct contact...
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b