Hi, You've provoked me to respond :-) but it is a good question so thanks for asking it.
Is it worth experimenting with the github issue tracker to see what it's like? If we decide to use some other system later we can probably export the github data via their API and move across. I worry that, if we wait to find the ideal system, we could be waiting a very long time (as that (originally French?) saying goes, "the perfect is the enemy of the good") The migration bug you mention-- is that still happening on XCP 1.6? It sounds familiar. Thanks, -- Dave Scott On Dec 22, 2012, at 7:26 PM, "George Shuklin" <george.shuk...@gmail.com> wrote: > I have some strange felling - developers are not (carefully) read that > maillist. > > Most of my bugreports are simply ignored. If I do pull request on > github, they are (at least) reviewed. But I'm not a real ocaml guru, so > many stuff I can report, but I can't fix. > > Where I can submit bugreports on XCP to be relatively sure I heard? > > For example: I found that every VM migration raise maxmem_kb few > kilobytes. Very large amount of iteration for migration cause very slow > 'maxmem_kb leak'. If I write about this here, I can be 100% sure that > no one will reacts. > > What shall I do? > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
