On December 25, 2010 03:10:28 pm namklim wrote: > So where should any test images be posted?
I have not seen / hit yet a file size limit on our Launchpad bug tracker [0]. If we do hit a limit, there is place on the panotools server. I can set up something on my own server too if needed. The bottom line is that if you put it on services like rapidshare or other "free" download sites, you make it difficult for me (and maybe for others too) to receive the files. > There was nothing in the original beta announcement indicating > where to post any problem images. There was (and it was the first or second paragraph) a statement to report bugs on Launchpad [0]. > I'd rather given up on testing/raising possible issues after posting > the images as there was no further follow-up or feedback. If you want follow up on issues or feedback, the bug tracker [0] is the place to go. And even then, don't expect a quick or immediate reply. People have other priorities than yours and you got to accept this (the same way I accept it if you decide that filing a report on Launchpad is not your priority and the issue goes unnoticed). > The problem occurred with all the Samyang panoramas I tried. File a bug report [0]. I don't have a Samyang lens. AFAIK the developers of cpfind don't have one either. I can't deal with what I don't know, and the chatter of a mailing list is not the right place to store this kind of information. I was cleaning up the backlog of mailing list messages and you are lucky that I had the time to actually read some of them and not just scan the subject lines. When I saw you kept coming back, I looked into it and quite frankly, without raising accusations, I found that people who replied to you misunderstand the issue; and not because they did not try to understand you. Speaking of which: meaningful subject lines attract attention. When I see "2010.4.0-beta1 Win32 test" I skip it, simply because I don't have Windows, I can't help, and it does not affect me. "cpfind does not find CP on Samyang fisheye images" would have attracted more attention, at least on my side. > I raised several issues in the original posting It is good practice to raise one issue in one bug ticket; and to put the issues in the bug tracker [0] (no, I won't stop repeating that). If you raise your issues anywhere else than in the bug tracker, don't expect anybody to pay attention or do anything about it. And if you raise multiple issues in a single message don't expect anybody to take the time and identify that there are multiple issues. > The CP problem with cpfind has only now, after a month been > picked up. This is not uncommon. Go into the bug tracker and you will find issues dating back to 2007. This is because people don't have time, and when they do they don't necessarily deal with your issues. > I have not checked in the RC whether the orphan instances > and the EXR issues have been resolved. I don't even know what you mean with "orphan instances". Regarding EXR, can it be [1]? As I stated, I read the subject saying "Win32 test" and I decided that this is not something I have time for. Was I wrong? of course I was. Why was I wrong? Yuv [0] https://bugs.launchpad.net/hugin [1] https://bugs.launchpad.net/hugin/+bug/678694
signature.asc
Description: This is a digitally signed message part.
