4:50 p.m.
Hello,
I would like to release po4a 0.41 within a couple of weeks. Is there
anything that should go into this release and is not already in SVN
trunk?
Denis
9:18 a.m.
New subject: [Po4a-devel] New release planned: po4a 0.41
On 2010/11/3 Denis Barbier wrote:
Hello,
I would like to release po4a 0.41 within a couple of weeks. Is there
anything that should go into this release and is not already in SVN
trunk?
Oops, I forgot to mention that a string has been modified in po/pod.
ca: po/pod/ca.po: 910t 87f 472u
es: po/pod/es.po: 1469t
fr: po/pod/fr.po: 1469t
it: po/pod/it.po: 389t 87f 993u
ja: po/pod/ja.po: 1468t 1f
pl: po/pod/pl.po: 1467t 2f
ru: po/pod/ru.po: 433t 31f 1005u
Denis
10:09 a.m.
New subject: [Po4a-devel] New release planned: po4a 0.41
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 04/11/2010 10:18, Denis Barbier a écrit :
On 2010/11/3 Denis Barbier wrote:
> Hello,
>
> I would like to release po4a 0.41 within a couple of weeks. Is there
> anything that should go into this release and is not already in SVN
> trunk?
Oops, I forgot to mention that a string has been modified in po/pod.
Would it be OK to perform an update call? Omar already did one last
time, so there may not be a lot more results, but we could also ask on
debian-i18n and debian-l10n lists (I'm note sure Omar used this one last
time) for new translations if that's OK. I volunteer to play with
podebconf-report-po unless Omar already did it or prefer to do it himself.
Would the usual +10days call be appropriate? Would a call for website
translation update be appropriate too?
Regards
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkzSzMUACgkQ18/WetbTC/pywACglWoOSFu3HmHlbx2vfx+vbVby
uiEAnRyngGtAlxtkdYv3rdX1edLhbpif
=nZL2
-----END PGP SIGNATURE-----
10:19 a.m.
New subject: [Po4a-devel] New release planned: po4a 0.41
On 2010/11/4 David Prévot wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 04/11/2010 10:18, Denis Barbier a écrit :
> On 2010/11/3 Denis Barbier wrote:
>> Hello,
>>
>> I would like to release po4a 0.41 within a couple of weeks. Is there
>> anything that should go into this release and is not already in SVN
>> trunk?
>
> Oops, I forgot to mention that a string has been modified in po/pod.
Would it be OK to perform an update call? Omar already did one last
time, so there may not be a lot more results, but we could also ask on
debian-i18n and debian-l10n lists (I'm note sure Omar used this one last
time) for new translations if that's OK. I volunteer to play with
podebconf-report-po unless Omar already did it or prefer to do it himself.
Would the usual +10days call be appropriate? Would a call for website
translation update be appropriate too?
I have no strong opinion about that. IMHO po4a 0.41 should go into
experimental, debian-release won't accept it into testing. If needed
we can make another release 0.40.2 which contains only translation
updates, this one could go into testing.
Denis
10:59 a.m.
New subject: [Po4a-devel] New release planned: po4a 0.41
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 04/11/2010 11:19, Denis Barbier a écrit :
On 2010/11/4 David Prévot wrote:
> Would it be OK to perform an update call? Omar already did one
last
> time, so there may not be a lot more results, but we could also ask on
> debian-i18n and debian-l10n lists (I'm note sure Omar used this one last
> time) for new translations if that's OK. I volunteer to play with
> podebconf-report-po unless Omar already did it or prefer to do it himself.
>
> Would the usual +10days call be appropriate? Would a call for website
> translation update be appropriate too?
I have no strong opinion about that. IMHO po4a 0.41 should go into
experimental, debian-release won't accept it into testing. If needed
Agreed.
we can make another release 0.40.2 which contains only translation
updates, this one could go into testing.
I wonder if the documentation changes in 0.41 would be accepted by the
RT: even if they just are “documentation fixes” and “translation
updates” that are willing to be accepted, the diff is huge and a lot of
Perl scripts are modified (no code is modified but the documentation is
in the same files).
If you think we could, I'm willing to prepare this documentation patch
and it makes sense to perform a call for translation for this release.
Anyway the Japanese and Polish translators are probably already
subscribed to this list, so it's not really an issue for the four
(nearly) up to date man-page translations, and ten days might not be
enough for the other ones (but it's not really a problem for 0.40.2 that
could be published later if new translations are performed).
If not, it still makes sense to do at least the call for runtime
(po/bin) translation since this one can easily be backported to 0.40.2.
Cheers
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkzS2GAACgkQ18/WetbTC/oQ5QCglJohdt37D/sOOG96n81OMk4g
Pq8AoIb5EA/J0xHybiH/suDwKYPnwimd
=LE7V
-----END PGP SIGNATURE-----
12:27 p.m.
New subject: [Po4a-devel] New release planned: po4a 0.41
On 2010/11/4 David Prévot wrote:
[...]
I wonder if the documentation changes in 0.41 would be accepted by
the
RT: even if they just are “documentation fixes” and “translation
updates” that are willing to be accepted, the diff is huge and a lot of
Perl scripts are modified (no code is modified but the documentation is
in the same files).
If you think we could, I'm willing to prepare this documentation patch
and it makes sense to perform a call for translation for this release.
[...]
AFAICT documentation changes are fine. So if you want to backport
your changes into 0.40.2, please go ahead.
I suggest the following approach:
- copy tags/0.40.1 into branches/0.40.x
- translators commit into trunk as usual
- changes are backported from trunk into branches/0.40.x
Would that work?
Denis
1:57 p.m.
New subject: [Po4a-devel] New release planned: po4a 0.41
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 04/11/2010 13:27, Denis Barbier a écrit :
On 2010/11/4 David Prévot wrote:
[...]
> I wonder if the documentation changes in 0.41 would be accepted by the
> RT: even if they just are “documentation fixes” and “translation
> updates” that are willing to be accepted, the diff is huge and a lot of
> Perl scripts are modified (no code is modified but the documentation is
> in the same files).
>
> If you think we could, I'm willing to prepare this documentation patch
> and it makes sense to perform a call for translation for this release.
[...]
AFAICT documentation changes are fine. So if you want to backport
your changes into 0.40.2, please go ahead.
I suggest the following approach:
- copy tags/0.40.1 into branches/0.40.x
- translators commit into trunk as usual
- changes are backported from trunk into branches/0.40.x
Would that work?
Great, I had something like that in mind, so I start the translation
call now, and will take care of backporting documentation stuff as soon
as possible.
Cheers
David (who would love to cherry-pick Subversion commits as easily as
Git's ones ;-).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkzTAhQACgkQ18/WetbTC/oqKQCfSsSM77+1kRLGdR+dSU/5GUcc
dbUAnRTAcNL/gDu5yj8b/wx1mR+F+zk2
=27NC
-----END PGP SIGNATURE-----
4:11 p.m.
New subject: [Po4a-devel] New release planned: po4a 0.41
On 2010/11/4 David Prévot wrote:
[...]
David (who would love to cherry-pick Subversion commits as easily as
Git's ones ;-).
You can :-)
Install git-svn and run
$ git svn clone -s svn://svn.debian.org/svn/po4a
It will takes some time to clone the SVN repository, but it is invaluable.
I guess that this is not recommended when merging between trunk and
another branch, but here you want to cherry-pick commits, thus git-svn
will work just fine.
Denis
9:08 a.m.
New subject: [Po4a-devel] New release planned: po4a 0.41
On 2010/11/3 Denis Barbier wrote:
Hello,
I would like to release po4a 0.41 within a couple of weeks. Is there
anything that should go into this release and is not already in SVN
trunk?
Hello,
I forgot to fix issues described in
https://bugzilla.redhat.com/show_bug.cgi?id=629931#c5
Those bugfixes won't introduce any new string, I will thus fix them in 0.41.
Denis
4921
days inactive
4933
days old
8 comments
2 participants
participants (2)
-
David Prévot -
Denis Barbier