Gaia/SMS/Scrum/1: Difference between revisions

 
(6 intermediate revisions by the same user not shown)
Line 45: Line 45:
|-
|-
! Day 10
! Day 10
|
| 5
|-
|-
! End
! End
|
| 0
|}
|}


Line 62: Line 62:


== Sprint planning ==
== Sprint planning ==
The minutes are stored [[Gaia/SMS/Scrum/Planning/2014-05-12|in a separate page]].
The minutes are stored [[Gaia/SMS/Scrum/1/Planning|in a separate page]].


== Daily meetings ==
== Daily meetings ==
Line 472: Line 472:
{{Line|Joan1|That's all}}
{{Line|Joan1|That's all}}
{{Line|Joan1|The regression is in contacts, and I have the solution}}
{{Line|Joan1|The regression is in contacts, and I have the solution}}
=== Day 10: May, 23th ===
{{Line|julienw|azasypkin, you're first !}}
{{Line|julienw|(random pick)}}
{{Line|azasypkin|ok :)}}
{{Line|azasypkin|Reviewed (mostly was testing on device) Julien's v1.3t patch for bug 1011573. Noted some odd behavior with invalid recipients;}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}1011573 nor, --, ---, felash, NEW, [B2G][Tarako][Messaging] Keyboard auto closes when editing the 'To' field in the messaging app}}
{{Line|azasypkin|Prepared and sent for review patch for bug 1013295}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}1013295 nor, --, ---, azasypkin, ASSI, [Messages] Migrated messages don't have a proper sentTimestamp}}
{{Line|azasypkin|patch allows to hide sent\received timestamp labels if corresponding timestamp isn't valid.}}
{{Line|azasypkin|Today will deal with review comments for bugs that are under review if any}}
{{Line|azasypkin|+ review Julien's navigation patch changes}}
{{Line|azasypkin|+ want to look into on bug 1014686 (follow-up from bug 963013)}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}1014686 nor, --, ---, azasypkin, NEW, [Messages][Refactoring] Improve "html template string" to "dom node\fragment" conversion}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}963013 nor, --, 2.0 S2 (23may), azasypkin, ASSI, [Messages][Refresh] Update bubbles style and layout of the thread.}}
{{Line|azasypkin|mm, can't remember what else}}
{{Line|azasypkin|that is it then :) next is schung }}
{{Line|schung|ok I just update the 1.3t bug about the lmk (bug 1008071)}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}1008071 nor, --, ---, schung, NEW, [Tarako][Messages]Sometimes attach Gallery image will cause Messages app be killed (not LMK)}}
{{Line|schung|I think we could not leave a serious block after that, so I fixed it and requested review  again}}
{{Line|schung|And reviewing the navigator patch again }}
{{Line|julienw|oki}}
{{Line|schung|Got some feedback from vicky in bug 1010093, might finish it when I have time}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}1010093 nor, --, 2.0 S3 (6june), schung, NEW, [Message] Visual refresh for delivery/read report icon in thread view}}
{{Line|schung|And take another 2.0 blocker bug 1009098 about compose regression}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}1009098 nor, --, ---, schung, NEW, [Messages] The "composer" is displayed in the "edit" mode}}
{{Line|schung|Oh BTW, I flash tarako in system instead of data/local }}
{{Line|julienw|ah !}}
{{Line|julienw|what was the issue ?}}
{{Line|schung|but we might need to remove wallpaper(since it was big) and make clean(it is important!)}}
{{Line|julienw|okay}}
{{Line|julienw|good to know !}}
{{Line|schung|Seems like a bug in build system if we don't clean it first}}
{{Line|julienw|anything else ?}}
{{Line|schung|I think that's all}}
{{Line|azasypkin|Oh, forgot to ask, julienw do you know if Joan is going to work on CSS part for bug 963013 on his last(?) day?}}
{{Line|azasypkin|bubble updates}}
{{Line|azasypkin|I see you've left a bunch of comments in PR}}
{{Line|julienw|I don't know}}
{{Line|julienw|maybe we can ask during the next comms standup meeting}}
{{Line|julienw|if he or arnau is here}}
{{Line|azasypkin|yep}}
{{Line|julienw|arnau seems connected on #fxos-comms, we can ask on IRC directly}}
{{Line|julienw|:)}}
{{Line|julienw|so my turn, quickly}}
{{Line|julienw|worked on bug 1011573 v1.3t+, I'm sad there are still issues ;)}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}1011573 nor, --, ---, felash, NEW, [B2G][Tarako][Messaging] Keyboard auto closes when editing the 'To' field in the messaging app}}
{{Line|julienw|will look at it first today because this needs to land today}}
{{Line|julienw|I'll also review in priority the patch from Steve for tarako as well}}
{{Line|julienw|yesterday I also handled your comments on the navigation patch bug 881469}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}881469 nor, --, 2.0 S2 (23may), felash, NEW, [MMS] Implement Navigation object}}
{{Line|julienw|so that we can have a review today and maybe land it before the end of the sprint}}
{{Line|julienw|I reviewed again the composer refresh from Joan, I think it might be able to land today, we'll see, otherwise we'll need to finish ourselves next week}}
{{Line|julienw|I also reviewed a change in the contact pick activity, seems like we have a "multipick" option now, so that the user can selects several contacts}}
{{Line|julienw|I might redirect the second review to one of you}}
{{Line|julienw|today I'll do the 2 v1.3t+ bugs in priority}}
{{Line|julienw|then handle your comments on the navigation patch (if any)}}
{{Line|julienw|and try to do most of my reviews}}
{{Line|julienw|and prepare next week sprint planning (I have some bugs to file for the visual refresh)}}
{{Line|schung|there is another message issue in tarako about the notification(bug 1010690). Is there anything we can do for this?}}
{{Line|firebot|Bug https://bugzilla.mozilla.org/show_bug.cgi?id{{=}}1010690 nor, --, 2.0 S2 (23may), sfoster, NEW, [Tarako][MMS][Notification] The notification of new MMS does not appear while playing music/video in}}
{{Line|julienw|I think this is a system issue }}
{{Line|julienw|because document.hidden is false !}}
{{Line|julienw|mmmm}}
{{Line|julienw|sorry another bug}}
{{Line|julienw|so here I don't know yet ;)}}
{{Line|julienw|I'll have a look}}
{{Line|schung|but the fallowing discussion didn't focus on that, that make me confuse}}
{{Line|julienw|there is another bug about the document.hidden issue}}
{{Line|julienw|I'll try to make sense of it :)}}
{{Line|julienw|ok I wanted to tell something about monday but I'll send you a mail instead because we're late}}
{{Line|julienw|let's go to the other stand up meeting ;)}}
{{Line|schung|see you later}}


== Demos ==
== Demos ==
Line 480: Line 554:


== Retrospective ==
== Retrospective ==
=== What was good in the last sprint ===
* we finished the sprint !
* I finished the navigation patch (at last !) yay :)
* I like that we discuss every day about SMS only things +1
* it was good to have the visual design team in the daily meetings
=== What was bad in the last sprint ===
* Still tones of blocker... (v1.3t/v1,4) Not sure when it will be ended
*:-> what can we do about this? at least try to know when it will finish?
*:-> Maybe that will help whether we should keep more resource on blockers
* It's still difficult for me to quickly find source of truth for VR (a lot of mocks, some of them outdated and etc.) +1
*:-> we already discussed about this with Victoria but nothing changed; let's discuss this again later today.+1
=== Any questions ===
* Could we have more easy way to update our status?  You mean, every day?Yep, for example, maybe we could have a google doc for bug id/status and we can update if before meeting(or update to wiki directly, we don't need to copy/paste everyday) and just update if something really blocked in the scrum.
*:The goal of the daily meeting is not really the status, it's more to discuss together. So I'm happy to change it to make it more useful. Oleg what are your thoughts?
*:Mmm, having some centralized doc\wiki (with bug<->status) will be good for Mon\Wed\Fri Comms meeting, not sure whether anyone else read our minutes. Regarding to daily meetings in IRC - I like it :)
*:Would it make sense to do the daily meeting partly in an etherpad too ? (like we do here now) We'd have etherpad for the bugs (and this way we can just add a line every day, for example) and IRC for other discussions
* is the sprint the right size? is 2 weeks fine? I think 2 is the right one, 1 is too small, 3 is too big.
=== Actions ===
* we need to know when the blocker phases end (especially when will 1.3t+ end?). +1
* have a centralized place for all uptodate visual design material
* daily meeting: use etherpad as a more synthetic way to update the bug status, and keep IRC as discussion backchannel(+1)
Confirmed users
820

edits