Nathan: Please send bugs via email to [email protected]. The receipt of the email will generate the ticket in the tracking system.
Please submit as much data as you can without giving away private information. Do not attach large files. Instead put them somewhere in AFS or elsewhere that is publicly accessible and includevthe location in the report. Thank you. Jeffrey Altman Sent from my iPad On Oct 3, 2011, at 5:30 PM, Nathaniel Hatley <[email protected]> wrote: > Good Morning, > > I have been working with Jeffrey Altman on various bugs that we've uncovered > on the OpenAFS Redirector with our new environment here at UNC Charlotte. > Given Jeffrey's recent submission of the redirector to the public tree, I > will need to start filing bugs with the OpenAFS bug tracking system. I have > not participated in OpenAFS' systems before, and would like to know the > correct methods of performing various actions. > > For example: I currently know of a bug that I've experienced that I see an > open ticket for in the bug tracker. I do not have an account on the tracker, > so I cannot post stating that I have also experienced this issue. Would this > be the correct behaviour? Or should I just submit an additional bug to > openafs-bugs and reference the previous bug number? > > Additionally, to what level of detail should I attempt to give when I submit > bugs? Typically if it is relevant, I will create procmon logs of the issue > and have them accessible via http. I also attempt to thoroughly describe the > environment with which I reproduced the issue. > > > Thank you, > Nathan Hatley
