Hello,
The issue of confidentiality has come up twice this past week for me so I
thought I'd send an email about it. Before you send emails to the mailing
list you should check that confidential information (e.g. molecule names
or perhaps even directory or project names) are not revealed. So if you
are including a stack trace for a bug report please check the stack trace
carefully. (But let us know that you have removed information so that we
don't get confused!)
The good news is that in 2.2.x (possibly x = 1) we will have a new bug
reporting system which will work from inside Analysis. It will allow the
stack trace to be sent to a private bug reporting database on our server.
(You will have the choice to send or not.) The one (potential) downside
is that bugs might not get mentioned on the mailing list as much (well,
some people might see that as an upside). We'll worry about how to deal
with that when we get to it, but I imagine that in relevant cases we'll
send out an email announcing the bug and (hopefully) its resolution.
Related to this, there will be a Registration popup from Analysis 2.2.1,
mainly so that we can keep better track of user numbers (important for
grant applications!), but it will also be useful for bug reports (if we
need to contact you for clarification, it's useful to know your email
address). Although you will not be forced to register, the dialog will
pop up every time you open a project (and maybe at other times) if you
haven't registered.
Wayne
|