...
I spoke with Mario and we agree to approve the Standards Changes for Epic/Sprint naming. Thanks!
Jeff
...
Email posted from Robyn on 17 August 2014:
Hello Jeff and Mario,
I copied over to the TCT Meeting notes your final acceptance of the issues discussed in this email thread when I realized that you accepted a Sprint Naming Policy but not the two standards in question!- Standards: should not shadow python built-in functions
- Changing the Python coding standard: == and != SHOULD be used when comparing to None
Apologies for not catching this earlier.
Email posted from Mario Juric on 18 August 2014:
On 8/17/14 20:22 , Robyn Allsman wrote:
> Hello Jeff and Mario,
> I copied over to the TCT Meeting notes your final acceptance of the
> issues discussed in this email thread when I realized that you accepted
> a Sprint Naming Policy but not the two standards in question!
>
> * *Standards: should not shadow python built-in functions*> Hello Jeff and Mario,
> I copied over to the TCT Meeting notes your final acceptance of the
> issues discussed in this email thread when I realized that you accepted
> a Sprint Naming Policy but not the two standards in question!
>
> * *Changing the Python coding standard: == and != SHOULD be used when
> comparing to None*
>
> Would you please review the SAT recommendation and the TCT comments
> noted in the attached email. And then provide your resolution for each
> proposed standard.
>
Given they were recommended by the SAT, I'd go forward and enact them> Would you please review the SAT recommendation and the TCT comments
> noted in the attached email. And then provide your resolution for each
> proposed standard.
>
(though I still have deep reservations about the first one; not worth
another round of SAT discussions, though...).
- M.
Action Items
@robyn - notify Jeff Kantor and Mario Juric about the TCT's lack of resolution on these Standards change requests.