On Fri, Jun 5, 2015 at 6:06 PM, kunaal jain <kunaalus@gmail.com> wrote:
> I am sorry modifying is wrong word. We will be using API, Hooks of bugzilla,
> which have excellent API, hooks.
>
> But since we will be doing experiments, it won't be a good idea using
> bugs.centos.org initially.

I understand that you will be testing things using the python-bugzilla
client or, similar to exercise the API. My question is, whether a
product named GSoC-Documentation-ToolChain (or, even an existing
documentation product) with a test-toolchain component would be
sufficient for you to check specifics of the issue sync. I am not very
clear about what exactly is being synchronized, would you be able to
point me to something I can read up. Or, explain the specifics of the
sync-and-test on this thread?

As long as you are not inadvertently DOS-ing the bugs.centos.org
instance by making incredibly high number of calls, you should perhaps
be well set there.

--
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel