[cle-release-team] Receiving emails from Jira?

[Matthew Jones]

Ah, I see, so they don't receive emails because the emails are going to the
cle-release-team at collab.sakaiproject.org.

If everyone on this list is okay getting notification of all these issues
that's fine. I wonder if we need 2 lists's one for jira notifications and
another for important release announcements (human generated). Or if
everyone on this (cle-release-team) list is just okay with filtering out
the jira noise client side if it's undesired. It has a pretty good
subscription, and I generally tell people to subscribe to become more
active in the community release, without remembering that they'll also get
a lot more jira notifications. ;)

Thanks.


On Wed, Oct 2, 2013 at 2:10 PM, Anthony Whyte <arwhyte at umich.edu> wrote:

> The msgcntr team Jira account has not been deleted (yet).  But it's
> associated email list has been whacked.
>
> I set all msgcntr component leads to the CLE team and set the default
> assignee the same as it is set in the SAK project.  Same was done for the
> OSP project.
>
> OSP is already part of SAK and as I noted last week it has no team so the
> account and email list reflect the past not the present.  Msgcntr is on its
> way to being merged into the SAK project.  We could assign the SAK msgcntr
> component lead to the msgcntr "team" (Bryan and Michelle principally if you
> look at svn logs) but that just perpetuates the balkanizing of the project.
>
> anthony whyte | its and mlibrary | university of michigan |
> arwhyte at umich.edu | 517-980-0228
>
>
> On Oct 2, 2013, at 1:50 PM, Matthew Jones wrote:
>
> The problem with this is that this email is the email for the user of the
> MSGCNTR Team group as that's the only way in jira to have multiple
> assignees to an issue (that I know of). If there's no longer a message
> center team and this user deleted (and all jiras assigned to a single
> individual) this makes sense.
>
> There are currently 6 special users connected to collab mailing lists.
> KERNEL TEAM   cle-kernel-team at collab.sakaiproject.org
> CLE TEAM   cle-release-team at collab.sakaiproject.org
> MSGCNTR Team   sakai-msgcntr-team at collab.sakaiproject.org
> OSP Jira Team   osp-jira at collab.sakaiproject.org
> SAMIGO TEAM   samigo at collab.sakaiproject.org
>  Sakai-Dev DG   sakai-dev at collab.sakaiproject.org
>
>
> On Wed, Oct 2, 2013 at 1:08 PM, Anthony Whyte <arwhyte at umich.edu> wrote:
>
>> It is.  The message team list was eliminated after checking first with
>> Megan May last week.
>>
>> As for the Message Center project in Jira, I switched the component leads
>> to the CLE team following the elimination of the msgcntr list.  Assuming
>> Bryan and Michelle, the two principle msgcntr committers do not object, I
>> plan to retire the Jira msgcntr project later this week after re-mapping
>> MSGCNTR ticket versions and merging its tickets to SAK.
>>
>> anthony whyte | its and mlibrary | university of michigan |
>> arwhyte at umich.edu | 517-980-0228
>>
>>
>> On Oct 2, 2013, at 12:23 PM, Matthew Jones wrote:
>>
>> I'm getting emails. This might be related to cleanup Anthony did on
>> INFRSTR-241. They have an alias on collab.sakaiproject.org to receive
>> their mail.
>>
>>
>>
>> On Wed, Oct 2, 2013 at 12:16 PM, Neal Caidin <neal.caidin at apereo.org>wrote:
>>
>>> Hi All,
>>>
>>> The MSGCNTR team is not receiving Jira emails since Friday.
>>>
>>> Before I investigate further, is anyone else experiencing this issue? If
>>> so, details are appreciated.
>>>
>>> Thanks,
>>> Neal
>>>
>>>
>>>
>>> Neal Caidin
>>> Sakai CLE Community Coordinator
>>> neal.caidin at apereo.org
>>> Skype: nealkdin
>>> Twitter: ncaidin
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> cle-release-team mailing list
>>> cle-release-team at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20131002/8c6b870b/attachment.html