Frank Schönheit - Sun Microsystems Germany wrote:
Hi Bernd,
Hi Frank,
This can even be automated (sic!), since for the feature mail, you need
to specify a project, anyway, which means the mail goes to
[EMAIL PROTECTED] Adding some additional "feedback to
[EMAIL PROTECTED]" should be easily possible, /me thinks.
Just adding that mentally to a
nice-to-have-and-probably-quickly-implementable-feature-wishes-for-eis-list
in my head.
Just noticed that interface announcements I sent today (via EIS, going
to [EMAIL PROTECTED]) contain a line
Send feedback to [email protected]
Is this a result of our discussion here?
Yes! And well it looks like it needs some adjustment after it´s first
incarnation.
I find it somewhat unfortunate: Even if I specify an affected project
(dba, in my case), then the line refers to [email protected], where it
should be [EMAIL PROTECTED]
That´s because it has been implemented just like suggested using the
"you need to specify a project, anyway" of a feature-mail. What we see
here is a side effect on an api-changes-mails which do not specify a
project defaulting to the developer mailing list than instead.
Also, for interface discussions, at least of general nature where no
particular project is affected, I'd say that
[EMAIL PROTECTED] is in fact the appropriate feedback
channel.
api-changes mails just have to be handled differently to feature-mails
*sigh*.
So the question is what shall we do for api changes mails as opposed to
feature-mails. Just always use [EMAIL PROTECTED] or look
at the ModulesAffected list and direct to appropiate project specific
list? If the later is the case what do we do if more than one module is
affected?
I think it would be best to just use interface-discuss for
api-changes-mails, what do you think?
Ciao
Frank
Ciao,
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
