www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-3338) Allow any address to post to wave-commits@incubator.apache.org
Date Tue, 11 Jan 2011 05:06:46 GMT

    [ https://issues.apache.org/jira/browse/INFRA-3338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979944#action_12979944
] 

Brett Porter commented on INFRA-3338:
-------------------------------------

Apologies, I had an extended discussion with Joe and found that it wasn't captured in my IRC
logs.

>From what I recall he said that the solution used before was to set up your review system
to send to the list via a single address, as the same thing had been done for Shindig in the
past. He might add more details if I've got that wrong.



> Allow any address to post to wave-commits@incubator.apache.org
> --------------------------------------------------------------
>
>                 Key: INFRA-3338
>                 URL: https://issues.apache.org/jira/browse/INFRA-3338
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Mail (qmail)
>            Reporter: Alex North
>
> The Wave project is in the process of moving from Google-hosted infrastructure to Apache
infra.
> Our existing "code discuss" mailing list receives commit messages, bug updates, and code
review requests. The first two come from wave-protocol@googlecode.com but the third are sent
by our code review tool as ("From") the logged in user, an arbitrary email address. This is
approximately what I think we should use the wave-commits@incubator.apache.org for, but when
I tried a test message from anorth@google.com it was rejected with "Must be sent from an @apache.org
address".
> Please allow any address to post to wave-commits@ for the time being, at least while
we're migrating systems to Apache infra. We may be able to tighten things back up again after
source, issues, and code review are all moved to Apache.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message