Please unsubscribe me, thanks

[Tarique Ansari]

CONFIDENTIALITY NOTICE: This email and attached material are intended for the 
use of the individual or organization to whom they are addressed and may not be 
distributed, copied, or disclosed to other unauthorized persons. This material 
may contain confidential and/or personal information subject to the provisions 
of the Freedom of Information and Protection of Privacy Act, the Municipal 
Freedom of Information and Protection of Privacy Act, and/or the Personal 
Health Information Protection Act. If you receive this transmission in error, 
please notify me immediately and delete this message. Do not email, print, 
copy, distribute, or disclose this email or its contents further. Thank you for 
your co-operation and assistance.

May 2015 Retrospective

[Ariel Weisberg]

Hi,

It's time. This month were are going to try and do the retrospective
in a Google
doc
.
Inside the docs I am guessing we will do a threaded conversation and sign
off contributions in the discussion section.

Last month things didn't thread well and it was hard to track what was
going on.

We released 2.1.5 in April so now is a good time to review anything you
fixed in 2.1.5 with an eye towards things that we would like to have done
better. You don't have to have an answer for how we could do things better.
We don't want to be limited to discussing things we already have answers
for.

If something is already being addressed (or is queued to be addressed by a
JIRA) there is no need to mention it unless you want +1 the issue for some
reason such as it not being prioritized sufficiently.

I am going to look at 2.1.5 the same way I didn't with 2.1.3, but I am
going to hold off on volunteering stuff until I see what people come with.

Regards,
Ariel

Re: May 2015 Retrospective

[Ariel Weisberg]

Hi,

Someone asked if they can add their own to went well/poorly/changes and the
answer is yes. We'll iterate on what goes up, but anyone can bring
something up for discussion. I don't think you should post a personal
well/poorly section, but you can post about things that went poorly for
just you. When something doesn't work for you it's not working for any of
us.

Ariel

On Mon, May 4, 2015 at 11:40 AM, Ariel Weisberg  wrote:

> Hi,
>
> It's time. This month were are going to try and do the retrospective in a 
> Google
> doc
> .
> Inside the docs I am guessing we will do a threaded conversation and sign
> off contributions in the discussion section.
>
> Last month things didn't thread well and it was hard to track what was
> going on.
>
> We released 2.1.5 in April so now is a good time to review anything you
> fixed in 2.1.5 with an eye towards things that we would like to have done
> better. You don't have to have an answer for how we could do things better.
> We don't want to be limited to discussing things we already have answers
> for.
>
> If something is already being addressed (or is queued to be addressed by a
> JIRA) there is no need to mention it unless you want +1 the issue for some
> reason such as it not being prioritized sufficiently.
>
> I am going to look at 2.1.5 the same way I didn't with 2.1.3, but I am
> going to hold off on volunteering stuff until I see what people come with.
>
> Regards,
> Ariel
>
>