From messages-noreply at linkedin.com Tue Aug 9 08:44:58 2011 From: messages-noreply at linkedin.com (Brian Klebash (Linkedin Groups)) Date: Tue, 9 Aug 2011 08:44:58 +0000 (UTC) Subject: [zanata-users] Brian Klebash invites you to join Commercial Real Estate Data Center Networking Group on LinkedIn Message-ID: <1861424709.7572775.1312879498516.JavaMail.app@ela4-app0128.prod> LinkedIn ------------ From: Brian Klebash Date: 8/09/2011 Subject: Brian Klebash invites you to join Commercial Real Estate Data Center Networking Group on LinkedIn Brian Klebash wrote: I would like to invite you to join my group on LinkedIn.

-Brian I don't want to receive these messages: http://www.linkedin.com/e/-b44xj9-gr4mk0er-1a/e7IrTLbLkbyYbvTWJ5YutE8LXbMQsRcRuFs2/blk/I1301105717_1/tD9MbOYWrSlI/prv/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bkearney at redhat.com Tue Aug 9 15:05:08 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 09 Aug 2011 11:05:08 -0400 Subject: [zanata-users] Usage Question: I have a patch Message-ID: <4E414CA4.9020508@redhat.com> I have a lifecycle question. For my zanata server, I have no idea if anyone is doing translations on the files I have uploaded. The community has given me a patch. I am not a translator, so there is no way for me to take the patch and apply it in zanata. If I apply the patches locally, and then upload the PO files, will I blow away any work done on the sevrer? -- bk From sflaniga at redhat.com Wed Aug 10 01:46:57 2011 From: sflaniga at redhat.com (Sean Flanigan) Date: Wed, 10 Aug 2011 11:46:57 +1000 Subject: [zanata-users] Usage Question: I have a patch In-Reply-To: <4E414CA4.9020508@redhat.com> References: <4E414CA4.9020508@redhat.com> Message-ID: <4E41E311.2000807@redhat.com> Hi Bryan, On 08/10/2011 01:05 AM, Bryan Kearney wrote: > I have a lifecycle question. For my zanata server, I have no idea if > anyone is doing translations on the files I have uploaded. As a workaround, you can see the stats against a project (View Status), or export PO files and diff them over time. But you're right, in some ways it's a bit hard to see what's happening inside Zanata. Feel free to submit a feature request in bugzilla if you have a suggestion. > The community > has given me a patch. I am not a translator, so there is no way for me > to take the patch and apply it in zanata. > If I apply the patches locally, and then upload the PO files, will I > blow away any work done on the sevrer? As of Zanata 1.3, you can just push the PO files, and the server will merge in any new strings. Any empty translations, or old translations, will be ignored. -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From bkearney at redhat.com Wed Aug 10 02:00:19 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Tue, 09 Aug 2011 22:00:19 -0400 Subject: [zanata-users] Usage Question: I have a patch In-Reply-To: <4E41E311.2000807@redhat.com> References: <4E414CA4.9020508@redhat.com> <4E41E311.2000807@redhat.com> Message-ID: <4E41E633.40508@redhat.com> On 08/09/2011 09:46 PM, Sean Flanigan wrote: > Hi Bryan, > > On 08/10/2011 01:05 AM, Bryan Kearney wrote: >> I have a lifecycle question. For my zanata server, I have no idea if >> anyone is doing translations on the files I have uploaded. > > As a workaround, you can see the stats against a project (View Status), > or export PO files and diff them over time. But you're right, in some > ways it's a bit hard to see what's happening inside Zanata. Feel free > to submit a feature request in bugzilla if you have a suggestion. > >> The community >> has given me a patch. I am not a translator, so there is no way for me >> to take the patch and apply it in zanata. > >> If I apply the patches locally, and then upload the PO files, will I >> blow away any work done on the sevrer? > > As of Zanata 1.3, you can just push the PO files, and the server will > merge in any new strings. Any empty translations, or old translations, > will be ignored. > > What are we using internally? If I can continue to push things, then I am fine. -- bk From bkearney at redhat.com Wed Aug 17 21:17:49 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Wed, 17 Aug 2011 17:17:49 -0400 Subject: [zanata-users] how do I control the directory name for pull and push Message-ID: <4E4C2FFD.2010103@redhat.com> I have the following directory layout: /home/bkearney/code/headpin/locale in locale, I have app.pot es/app.po fr/app.po If I want to load to the server, I seem to be able to do the following: zanata publican push --srcdir . --import-po and it finds the *.po files fine. However, trying to do a po pull or a publican pull seems to want to put them into /home/bkearney/code/headpin/locale/po/ is there a way to skip that po directory being added? -- bk From sflaniga at redhat.com Thu Aug 18 01:26:01 2011 From: sflaniga at redhat.com (Sean Flanigan) Date: Thu, 18 Aug 2011 11:26:01 +1000 Subject: [zanata-users] how do I control the directory name for pull and push In-Reply-To: <4E4C2FFD.2010103@redhat.com> References: <4E4C2FFD.2010103@redhat.com> Message-ID: <4E4C6A29.8030708@redhat.com> On 08/18/2011 07:17 AM, Bryan Kearney wrote: > I have the following directory layout: > > /home/bkearney/code/headpin/locale > > in locale, I have > app.pot > es/app.po > fr/app.po > > If I want to load to the server, I seem to be able to do the following: > > > zanata publican push --srcdir . --import-po > > > and it finds the *.po files fine. However, trying to do a po pull or a > publican pull seems to want to put them into > > /home/bkearney/code/headpin/locale/po/ > > is there a way to skip that po directory being added? I'm not so familiar with the python client, and I'm not sure which version you've got, but have you tried the --transdir (formerly --dstdir) option? If that doesn't help, you've probably found a bug in the client. In that case, for now I can only suggest that you use a symlink as a workaround. ("ln -s po .") Sorry. The new commands "zanata push" and "zanata pull" will have saner directory handling. -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: From dchen at redhat.com Thu Aug 18 01:55:50 2011 From: dchen at redhat.com (Ding Yi Chen) Date: Wed, 17 Aug 2011 21:55:50 -0400 (EDT) Subject: [zanata-users] how do I control the directory name for pull and push In-Reply-To: <4E4C6A29.8030708@redhat.com> Message-ID: <1248208558.2735497.1313632550574.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> ----- Original Message ----- > On 08/18/2011 07:17 AM, Bryan Kearney wrote: > > I have the following directory layout: > > > > /home/bkearney/code/headpin/locale > > > > in locale, I have > > app.pot > > es/app.po > > fr/app.po > > > > If I want to load to the server, I seem to be able to do the > > following: > > > > > > zanata publican push --srcdir . --import-po > > > > > > and it finds the *.po files fine. However, trying to do a po pull or > > a > > publican pull seems to want to put them into > > > > /home/bkearney/code/headpin/locale/po/ > > > > is there a way to skip that po directory being added? > > > I'm not so familiar with the python client, and I'm not sure which > version you've got, but have you tried the --transdir (formerly > --dstdir) option? If that doesn't help, you've probably found a bug in > the client. > > In that case, for now I can only suggest that you use a symlink as a > workaround. ("ln -s po .") Sorry. The new commands "zanata push" and > "zanata pull" will have saner directory handling. This is reported as https://bugzilla.redhat.com/show_bug.cgi?id=730200 The one in Git is fixed, but the fix has not yet released. Regards, -- Ding-Yi Chen Software Engineer Internationalization Group Red Hat, Inc. Register now for Red Hat Virtual Experience, December 9. Enterprise Linux, virtualization, cloud, and more. http://www.redhat.com/virtualexperience From bkearney at redhat.com Thu Aug 18 12:08:50 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 18 Aug 2011 08:08:50 -0400 Subject: [zanata-users] how do I control the directory name for pull and push In-Reply-To: <1248208558.2735497.1313632550574.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> References: <1248208558.2735497.1313632550574.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> Message-ID: <4E4D00D2.404@redhat.com> On 08/17/2011 09:55 PM, Ding Yi Chen wrote: > > > ----- Original Message ----- >> On 08/18/2011 07:17 AM, Bryan Kearney wrote: >>> I have the following directory layout: >>> >>> /home/bkearney/code/headpin/locale >>> >>> in locale, I have >>> app.pot >>> es/app.po >>> fr/app.po >>> >>> If I want to load to the server, I seem to be able to do the >>> following: >>> >>> >>> zanata publican push --srcdir . --import-po >>> >>> >>> and it finds the *.po files fine. However, trying to do a po pull or >>> a >>> publican pull seems to want to put them into >>> >>> /home/bkearney/code/headpin/locale/po/ >>> >>> is there a way to skip that po directory being added? >> >> >> I'm not so familiar with the python client, and I'm not sure which >> version you've got, but have you tried the --transdir (formerly >> --dstdir) option? If that doesn't help, you've probably found a bug in >> the client. >> >> In that case, for now I can only suggest that you use a symlink as a >> workaround. ("ln -s po .") Sorry. The new commands "zanata push" and >> "zanata pull" will have saner directory handling. > > This is reported as https://bugzilla.redhat.com/show_bug.cgi?id=730200 > The one in Git is fixed, but the fix has not yet released. Will do the work around. Do you have an estimate on the next release for fedora? -- bk From bkearney at redhat.com Thu Aug 18 12:24:42 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 18 Aug 2011 08:24:42 -0400 Subject: [zanata-users] how do I control the directory name for pull and push In-Reply-To: <4E4D00D2.404@redhat.com> References: <1248208558.2735497.1313632550574.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com> <4E4D00D2.404@redhat.com> Message-ID: <4E4D048A.2070202@redhat.com> On 08/18/2011 08:08 AM, Bryan Kearney wrote: > On 08/17/2011 09:55 PM, Ding Yi Chen wrote: >> >> >> ----- Original Message ----- >>> On 08/18/2011 07:17 AM, Bryan Kearney wrote: >>>> I have the following directory layout: >>>> >>>> /home/bkearney/code/headpin/locale >>>> >>>> in locale, I have >>>> app.pot >>>> es/app.po >>>> fr/app.po >>>> >>>> If I want to load to the server, I seem to be able to do the >>>> following: >>>> >>>> >>>> zanata publican push --srcdir . --import-po >>>> >>>> >>>> and it finds the *.po files fine. However, trying to do a po pull or >>>> a >>>> publican pull seems to want to put them into >>>> >>>> /home/bkearney/code/headpin/locale/po/ >>>> >>>> is there a way to skip that po directory being added? >>> >>> >>> I'm not so familiar with the python client, and I'm not sure which >>> version you've got, but have you tried the --transdir (formerly >>> --dstdir) option? If that doesn't help, you've probably found a bug in >>> the client. >>> >>> In that case, for now I can only suggest that you use a symlink as a >>> workaround. ("ln -s po .") Sorry. The new commands "zanata push" and >>> "zanata pull" will have saner directory handling. >> >> This is reported as https://bugzilla.redhat.com/show_bug.cgi?id=730200 >> The one in Git is fixed, but the fix has not yet released. > > > Will do the work around. Do you have an estimate on the next release for > fedora? I pulled the latest from git, did a make install, and I do not see that this is fixed. All of these seem to result in a po directory being used: zanata publican pull --dstdir . zanata publican pull --transdir . zanata po pull --dstdir . zanata po pull --transdir . -- bk From bkearney at redhat.com Thu Aug 18 13:33:09 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Thu, 18 Aug 2011 09:33:09 -0400 Subject: [zanata-users] Logical Server name Message-ID: <4E4D1495.5060707@redhat.com> Put in this RFE: https://bugzilla.redhat.com/show_bug.cgi?id=731722 We would like to see a level of abstracting between the zanata.xml file and the url of the server. This will allow us to check in the files evern though the reference private server names. -- bk From jni at redhat.com Fri Aug 19 02:14:00 2011 From: jni at redhat.com (James Ni) Date: Thu, 18 Aug 2011 22:14:00 -0400 (EDT) Subject: [zanata-users] how do I control the directory name for pull and push In-Reply-To: <4E4D048A.2070202@redhat.com> Message-ID: <75317881.847566.1313720040421.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Hi, Bryan I am quite confused about your issues So you running 'zanata publican push' under /home/bkearney/code/headpin/locale ? And you running 'zanata publican pull' under same folder? For current implementation, 'zanata publican pull' should always save translation to locale folder, say zh-CN, or ja-JP. It should works fine. So could you give more info about issues or try the latest code again? Maybe you can tell me the project you are working with and i can try to pull it and see what happens. I am on IRC #doc-i18n and #l10n channel, jni is my nickname, we could discuss this on IRC, thanks Best Regards ----- Original Message ----- > On 08/18/2011 08:08 AM, Bryan Kearney wrote: > > On 08/17/2011 09:55 PM, Ding Yi Chen wrote: > >> > >> > >> ----- Original Message ----- > >>> On 08/18/2011 07:17 AM, Bryan Kearney wrote: > >>>> I have the following directory layout: > >>>> > >>>> /home/bkearney/code/headpin/locale > >>>> > >>>> in locale, I have > >>>> app.pot > >>>> es/app.po > >>>> fr/app.po > >>>> > >>>> If I want to load to the server, I seem to be able to do the > >>>> following: > >>>> > >>>> > >>>> zanata publican push --srcdir . --import-po > >>>> > >>>> > >>>> and it finds the *.po files fine. However, trying to do a po pull > >>>> or > >>>> a > >>>> publican pull seems to want to put them into > >>>> > >>>> /home/bkearney/code/headpin/locale/po/ > >>>> > >>>> is there a way to skip that po directory being added? > >>> > >>> > >>> I'm not so familiar with the python client, and I'm not sure which > >>> version you've got, but have you tried the --transdir (formerly > >>> --dstdir) option? If that doesn't help, you've probably found a > >>> bug in > >>> the client. > >>> > >>> In that case, for now I can only suggest that you use a symlink as > >>> a > >>> workaround. ("ln -s po .") Sorry. The new commands "zanata push" > >>> and > >>> "zanata pull" will have saner directory handling. > >> > >> This is reported as > >> https://bugzilla.redhat.com/show_bug.cgi?id=730200 > >> The one in Git is fixed, but the fix has not yet released. > > > > > > Will do the work around. Do you have an estimate on the next release > > for > > fedora? > > I pulled the latest from git, did a make install, and I do not see > that > this is fixed. All of these seem to result in a po directory being > used: > > zanata publican pull --dstdir . > zanata publican pull --transdir . > zanata po pull --dstdir . > zanata po pull --transdir . > > -- bk > > _______________________________________________ > zanata-users mailing list > zanata-users at redhat.com > https://www.redhat.com/mailman/listinfo/zanata-users From bkearney at redhat.com Fri Aug 19 12:09:05 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Fri, 19 Aug 2011 08:09:05 -0400 Subject: [zanata-users] how do I control the directory name for pull and push In-Reply-To: <75317881.847566.1313720040421.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> References: <75317881.847566.1313720040421.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <4E4E5261.3090109@redhat.com> On 08/18/2011 10:14 PM, James Ni wrote: > Hi, Bryan > > I am quite confused about your issues > So you running 'zanata publican push' under /home/bkearney/code/headpin/locale ? > And you running 'zanata publican pull' under same folder? > > For current implementation, 'zanata publican pull' should always save translation to locale folder, say zh-CN, or ja-JP. It should works fine. > So could you give more info about issues or try the latest code again? > Maybe you can tell me the project you are working with and i can try to pull it and see what happens. > > I am on IRC #doc-i18n and #l10n channel, jni is my nickname, we could discuss this on IRC, thanks > > Best Regards > Please see http://pastie.org/2396387. Note on line 16 that it is appending /po to the current directory. I would like it not have it append po to my directory. Adding --dir seems to have no effect. -- bk From jni at redhat.com Mon Aug 22 01:46:01 2011 From: jni at redhat.com (James Ni) Date: Sun, 21 Aug 2011 21:46:01 -0400 (EDT) Subject: [zanata-users] how do I control the directory name for pull and push In-Reply-To: <4E4E5261.3090109@redhat.com> Message-ID: <15131920.869392.1313977561843.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Hi, Bryan Thanks, i have test the latest code with Headpin 1.0 on https://translate.engineering.redhat.com, it works fine, Do you pull the source code from https://github.com/zanata/zanata-python-client? If you pull the source code from my repo(https://github.com/jamesni/zanata-python-client), the source code on that repo is old. I should sorry for moving the source code to https://github.com/zanata/zanata-python-client without any announcement. Please download source code from that repo. The version display for client should be 1.2.6-3-g8f49, i will add a zanata version command, and release 1.3.0 this week Best Regards James ----- Original Message ----- > On 08/18/2011 10:14 PM, James Ni wrote: > > Hi, Bryan > > > > I am quite confused about your issues > > So you running 'zanata publican push' under > > /home/bkearney/code/headpin/locale ? > > And you running 'zanata publican pull' under same folder? > > > > For current implementation, 'zanata publican pull' should always > > save translation to locale folder, say zh-CN, or ja-JP. It should > > works fine. > > So could you give more info about issues or try the latest code > > again? > > Maybe you can tell me the project you are working with and i can try > > to pull it and see what happens. > > > > I am on IRC #doc-i18n and #l10n channel, jni is my nickname, we > > could discuss this on IRC, thanks > > > > Best Regards > > > > Please see http://pastie.org/2396387. Note on line 16 that it is > appending /po to the current directory. I would like it not have it > append po to my directory. Adding --dir seems to have no effect. > > -- bk From bkearney at redhat.com Mon Aug 22 12:45:14 2011 From: bkearney at redhat.com (Bryan Kearney) Date: Mon, 22 Aug 2011 08:45:14 -0400 Subject: [zanata-users] how do I control the directory name for pull and push In-Reply-To: <15131920.869392.1313977561843.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> References: <15131920.869392.1313977561843.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <4E524F5A.5030600@redhat.com> On 08/21/2011 09:46 PM, James Ni wrote: > Hi, Bryan > > Thanks, i have test the latest code with Headpin 1.0 on https://translate.engineering.redhat.com, it works fine, Do you pull the source code from https://github.com/zanata/zanata-python-client? If you pull the source code from my repo(https://github.com/jamesni/zanata-python-client), the source code on that repo is old. I should sorry for moving the source code to https://github.com/zanata/zanata-python-client without any announcement. Please download source code from that repo. > > The version display for client should be 1.2.6-3-g8f49, i will add a zanata version command, and release 1.3.0 this week > > Best Regards > > James I have hte latest.. working much better. Thanks! -- bk From jni at redhat.com Wed Aug 24 05:22:50 2011 From: jni at redhat.com (James Ni) Date: Wed, 24 Aug 2011 01:22:50 -0400 (EDT) Subject: [zanata-users] release version 1.3.0 of zanata-python-client In-Reply-To: <1329089470.904354.1314155501923.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <1774632665.905322.1314163370879.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Hi I just make a new package for zanata python client, version 1.3.0, for RHEL 5, 6, Fedora 14 and Fedora 15. You can find them on koji or using yum install to install it. If you are interested in source code, please download source code from github: https://github.com/zanata/zanata-python-client, please note that the source code on my personal repo: https://github.com/jamesni is old and may not update frequently. The main improvement for 1.3.0: -Add support for import and export fuzzy entry -Add python-httplib2-0.4.0-5.el6 requirement, since python-httplib2 have some issues with python 2.6 on RHEL 6 -Change project type to gettext for software and podir for publican -Add --version and -V options to display python client version There are some features will be implemented in the next release soon: --msgctxt support python client doesn't support it in current version and server also doesn't store the msgctxt --locale mapping we will try to add locale mapping in zanata.xml or processing it on server side. --project type This info will include in zanata.xml --glossary support We will use python client to push glossary to server If you have any concerns or issues about the python client, please send to me or send to zanata-list at redhat.com and zanata-users at redhat.com You can also find me (nickname: jni) on #l10n channel on IRC. Thanks. Best Regards James Ni From mospina at redhat.com Thu Aug 25 00:47:27 2011 From: mospina at redhat.com (Manuel Ospina) Date: Wed, 24 Aug 2011 20:47:27 -0400 (EDT) Subject: [zanata-users] release version 1.3.0 of zanata-python-client In-Reply-To: <1774632665.905322.1314163370879.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <511318553.923024.1314233247805.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Hello James, Thank you for the new release. I tried to update the package but it seems it's not in the repositories yet. Can you please send me the URL of koji where I can get the RPM? Regards, Manuel ----- Original Message ----- From: "James Ni" To: "zanata-list" , "Manuel Eduardo Ospina Sarmiento" , "Yu Shao" , "Sean Flanigan" , "Jens-Ulrik Petersen" , "Yi Chen, Ding" Cc: "zanata-users" , "zanata-devel" Sent: Wednesday, August 24, 2011 3:22:50 PM Subject: release version 1.3.0 of zanata-python-client Hi I just make a new package for zanata python client, version 1.3.0, for RHEL 5, 6, Fedora 14 and Fedora 15. You can find them on koji or using yum install to install it. If you are interested in source code, please download source code from github: https://github.com/zanata/zanata-python-client, please note that the source code on my personal repo: https://github.com/jamesni is old and may not update frequently. The main improvement for 1.3.0: -Add support for import and export fuzzy entry -Add python-httplib2-0.4.0-5.el6 requirement, since python-httplib2 have some issues with python 2.6 on RHEL 6 -Change project type to gettext for software and podir for publican -Add --version and -V options to display python client version There are some features will be implemented in the next release soon: --msgctxt support python client doesn't support it in current version and server also doesn't store the msgctxt --locale mapping we will try to add locale mapping in zanata.xml or processing it on server side. --project type This info will include in zanata.xml --glossary support We will use python client to push glossary to server If you have any concerns or issues about the python client, please send to me or send to zanata-list at redhat.com and zanata-users at redhat.com You can also find me (nickname: jni) on #l10n channel on IRC. Thanks. Best Regards James Ni -- Manuel Ospina Supervisor, Localization Services Red Hat Asia-Pacific Phone: +61 7 3514 8112 From petersen at redhat.com Thu Aug 25 01:11:29 2011 From: petersen at redhat.com (Jens Petersen) Date: Wed, 24 Aug 2011 21:11:29 -0400 (EDT) Subject: [zanata-users] release version 1.3.0 of zanata-python-client In-Reply-To: <511318553.923024.1314233247805.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <2052873010.1272413.1314234689030.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Manuel, you can find Fedora and EPEL updates in Bodhi: https://admin.fedoraproject.org/updates/zanata-python-client and Koji: http://koji.fedoraproject.org/koji/packageinfo?packageID=zanata-python-client The Fedora updates are still in testing you can install them with yum (as an auto-comment in bugzilla from Bodhi would tell you) using: $ sudo yum --enablerepo=updates-testing update zanata-python-client before they reach the stable updates repo. James: you should list the bugzilla numbers you fix in the updates. I guess you moved all the Fedora product issues to the Zanata product? That makes them a harder for Fedora users to find though... Cheers, Jens From jni at redhat.com Thu Aug 25 02:00:45 2011 From: jni at redhat.com (James Ni) Date: Wed, 24 Aug 2011 22:00:45 -0400 (EDT) Subject: [zanata-users] release version 1.3.0 of zanata-python-client In-Reply-To: <2052873010.1272413.1314234689030.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <1375312982.923973.1314237645157.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Hi, Jens Thanks, bugs are committed to zanata product directly at beginning, so we don't move them from fedora product to zanata product. The bug fixed is: Bug 727386 - zanata po push does not assume working directory Bug 728821 - Fuzzy strings are not shown on web interface after uploading Bug 730606 - The fuzzies entries from an imported PO file appear as translated in the zanata workspace Bug 726558 - Zanata deployment issue in RHEL6 Some issue like rename --project-type option, we don't have a corresponding bug for that. Do you think we need commit python client bug as Fedora product? or we still commit it as Zanata product? Best Regards James ----- Original Message ----- > Manuel, you can find Fedora and EPEL updates in Bodhi: > > https://admin.fedoraproject.org/updates/zanata-python-client > > and Koji: > > http://koji.fedoraproject.org/koji/packageinfo?packageID=zanata-python-client > > The Fedora updates are still in testing you can install them > with yum (as an auto-comment in bugzilla from Bodhi would tell you) > using: > > $ sudo yum --enablerepo=updates-testing update zanata-python-client > > before they reach the stable updates repo. > > James: you should list the bugzilla numbers you fix in the updates. > I guess you moved all the Fedora product issues to the Zanata product? > That makes them a harder for Fedora users to find though... > > Cheers, Jens From petersen at redhat.com Thu Aug 25 03:06:59 2011 From: petersen at redhat.com (Jens Petersen) Date: Wed, 24 Aug 2011 23:06:59 -0400 (EDT) Subject: [zanata-users] release version 1.3.0 of zanata-python-client In-Reply-To: <1375312982.923973.1314237645157.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com> Message-ID: <977907750.1273434.1314241619268.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Hi James, > Do you think we need commit python client bug as Fedora product? or we > still commit it as Zanata product? I think Fedora users who don't know "better" will report bugs against zanata-python-client under the Fedora product in Bugzilla. In fact I was surprised not to find any bugs there... ;) Asking people to use the Zanata product to search and report bugs for a Fedora package is unintuitive and more work for them. Currently the user-base may be contained/educated enough for this to work but this will change when more general users pick up the package... Strictly the Zanata product is for upstream and that is ok too for the server-side service I guess - for the python client package I feel using the Fedora product is more natural. That's my 2 yen anyway... Jens From sflaniga at redhat.com Thu Aug 25 03:19:09 2011 From: sflaniga at redhat.com (Sean Flanigan) Date: Thu, 25 Aug 2011 13:19:09 +1000 Subject: [zanata-users] release version 1.3.0 of zanata-python-client In-Reply-To: <977907750.1273434.1314241619268.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> References: <977907750.1273434.1314241619268.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <4E55BF2D.1080701@redhat.com> On 08/25/2011 01:06 PM, Jens Petersen wrote: > Hi James, > >> Do you think we need commit python client bug as Fedora product? or we >> still commit it as Zanata product? > > I think Fedora users who don't know "better" will report bugs > against zanata-python-client under the Fedora product in Bugzilla. > In fact I was surprised not to find any bugs there... ;) > > Asking people to use the Zanata product to search and report bugs for > a Fedora package is unintuitive and more work for them. > Currently the user-base may be contained/educated enough for this to work > but this will change when more general users pick up the package... > > Strictly the Zanata product is for upstream and that is ok too for the server-side service > I guess - for the python client package I feel using the Fedora product is more natural. > > That's my 2 yen anyway... > > Jens If you're reporting a bug against a released version of the fedora package zanata-python-client, (or rawhide, I suppose), you *should* use zanata-python-client under the Fedora product. Sometimes the fix is just to release a new version of the package, because it's fixed upstream in git, or it's a dependency problem. In other cases, we should create a second, upstream bug against the Zanata product, so that we can schedule it for a sprint, and make use of the custom fields in Bugzilla. However, if you're running the client directly from git, you should report against the upstream Zanata product. That way, bugs which are found by the development team (for instance) before release don't clog up the Fedora package. -- Sean Flanigan Senior Software Engineer Engineering - Internationalisation Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: