You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@infra.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2014/01/18 03:06:19 UTC

[jira] [Assigned] (INFRA-7180) Rename issues@jclouds.a.o -> notifications@jclouds.a.o

     [ https://issues.apache.org/jira/browse/INFRA-7180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin reassigned INFRA-7180:
----------------------------

    Assignee: Gavin

> Rename issues@jclouds.a.o -> notifications@jclouds.a.o
> ------------------------------------------------------
>
>                 Key: INFRA-7180
>                 URL: https://issues.apache.org/jira/browse/INFRA-7180
>             Project: Infrastructure
>          Issue Type: Task
>            Reporter: Andrew Phillips
>            Assignee: Gavin
>
> Following discussions in the jclouds community [1], we would like to rename issues@jclouds.apache.org (created as part of INFRA-6210) to notifications@jclouds.apache.org.
> As advised on #asfinfra, a ticket is the easiest way to do this.
> Two quick additional questions:
> 1. Could you also update the JIRA notification preferences for the JCLOUDS project so JIRA emails go to notifications@, or would a JCLOUDS project admin need to do this?
> 2. Could you ensure dev@jclouds.apache.org is *not* subscribed to notifications@? If this is not possible, who would need to make this request - one of the dev@ moderators, I presume?
> Thanks!
> Andrew
> [1] http://markmail.org/thread/56h7ranonrfqlukr



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)