Teammates: Release V5.103

[whipermr5]

Scheduled for May 10, 2017, 11.59pm SGT.

[whipermr5]

Release 252

Code Contributions from: @boxin-yang, @HirdayGupta, @Malkone, @whipermr5, @thejosharcher, @kguo901, @Mynk96, @nassimbg, @rchliu, @saching97, @samsontmr, @shrut1996, @sdweber422, @Subh0m0y, @sujeet14108, @VamsiSangam, @wkurniawan07, @xpdavid, @Yogitha6
Review Contributions from: @damithc, @Neurrone, @whipermr5, @junhaoyap, @ablyx, @thenaesh, @wkurniawan07, @xpdavid, @leeyimin, @chowyb

Sprint Period: Apr 17, 2017 - May 10, 2017
Sprint Velocity: 66 hrs (code) + 41 hrs (review) = 107 hrs (total)

[VamsiSangam]

Just curious... How did you calculate the hours of code and review?

[whipermr5]

@VamsiSangam I summed up the e.* effort labels. They're added by team members as an estimate of the number of hours required for coding (tagged to the issue) and reviewing (tagged to the PR).

[VamsiSangam]

Wow that's cool. 😲 Thanks!

[Yogitha6]

@whipermr5 , after looking at this post, I thought the website with this latest code has been deployed, however when I access TEAMMATES website, I can't find the new changes. Am I doing something wrong ?
(Just curious 😄)

[whipermr5]

@Yogitha6 There are still several steps @damithc has to take before that, e.g. testing on the live server and making the new version default. Once it's fully deployed, this issue will be closed :)

[damithc]

@VamsiSangam I summed up the e.* effort labels. They're added by team members as an estimate of the number of hours required for coding (tagged to the issue) and reviewing (tagged to the PR).

@VamsiSangam note that these hours may not match the actual clock time spent. It's just a relative measure we use to keep track of our velocity.
@whipermr5 may be use a different name for the measurement units, to avoid misunderstandings?. XP/Scrum folks use 'story points' (as they use user stories for tracking requirements). We can simply call them 'points' or 'effort points'.

[VamsiSangam]

Yes sir I understand that 😄

[damithc]

Deployed