MozillaWiki

Firefox/Iterative Hello Development: Difference between revisions

Page Discussion

Firefox/Iterative Hello Development (view source)

Revision as of 14:29, 18 May 2015

1,239 bytes removed ,  18 May 2015
updated for firefox 40
(updated for firefox 40)
Line 68: Line 68:


===Current===
===Current===
====Iteration 40.3 (through May 11)====
 
* Context work:  Server update deployed.  Majority of Client side landed - but did not stay.  was not passing QA tests.  Troubleshooting to identify cause.  Edit is still landing - in review.  
====Iteration 41.1 (through May 25)====
* Functional test work broken down - and only top 2 items are 100% blockers to be addressed 40.3 or 41.1 - rest will be taken with backlog.
* Context work: should move to testing with this iteration and uplift. All strings needed were uplifted.   
* break-down/UX clarification for Link-clicker and in-conversation chat continue
* Affiliate work: working on and ideally landing this iteration - barring unforseen surprises
* Chat: test of the SDK functionality was successful - UX not implemented to design.
* Functional test work broken down - and only top 2 items are 100% blockers to be addressed in 41.1
**  If time, telemetry patches (marked Metrics in Backlog).  They are low risk/small changes and vital to making informed decisions, we will be requesting uplift to 39 for those landing in this iteration.
**  If time, telemetry patches (marked Metrics in Backlog).  They are low risk/small changes and vital to making informed decisions, we will be requesting uplift to 39 for those landing in this iteration.
'''All bugs marked with this iteration'''
'''All bugs marked with this iteration'''
Line 79: Line 81:
         "product":["Loop"],  
         "product":["Loop"],  
         "include_fields":"id, summary, status, assigned_to, cf_fx_points",
         "include_fields":"id, summary, status, assigned_to, cf_fx_points",
         "cf_fx_iteration":"40.3 - 11 May"
         "cf_fx_iteration":"41.1 - May 25"


}
}
Line 87: Line 89:


===Past===
===Past===
====Iteration 40.2 (through April 27)====
 
* Shareplane landed and verified and uplifting to Fx39.
====Firefox Release 40 Dev stage (ended May 11)====
* Adding more Google Analytic metrics for stand-alone client (link clicker)
* Context work:
* Context work:
**  Server end: [https://etherpad.mozilla.org/loopcrossteam 0.17.4] has hit bumps with updated module causing failure and is currently diagnosing 503 errors before deploying.
**  Server end: [https://etherpad.mozilla.org/loopcrossteam 0.17.4] has hit bumps with updated module causing failure and is currently diagnosing 503 errors before deploying.
**  Client-end: Continues through at least this iteration. Discovered issue with encryption key generation that will require re-authentication after upgrade, working on UX change now.
**  Client-end: Continues through at least this iteration. Discovered issue with encryption key generation that will require re-authentication after upgrade, working on UX change now.
* Quality focus this release on reviewing results of data gathered and identifying likely causes/implementing fixes.
* Shareplane landed and verified and uplifting to Fx39.
* Added more Google Analytic metrics for stand-alone client (link clicker)
* Continuing [https://bugzilla.mozilla.org/show_bug.cgi?id=1141296 CSS clean-up in SDK] and how that impacts Hello code. starting landing small pieces - as it's pretty tangled - and keep spinning off and landing more.
* Continuing [https://bugzilla.mozilla.org/show_bug.cgi?id=1141296 CSS clean-up in SDK] and how that impacts Hello code. starting landing small pieces - as it's pretty tangled - and keep spinning off and landing more.
* break-down/UX clarification for Link-clicker and in-conversation chat continue
* Functional test work broken down - these are areas that help speed development and lower risk, making it simpler to catch errors and regressions sooner.
**broke link-clicker work into 2 distinct parts.  first part is "i am always me".
* Metrics
**  If time, telemetry patches (marked Metrics in Backlog).  They are low risk/small changes and vital to making informed decisions, we will be requesting uplift to 39 for those landing in this iteration.
'''All bugs marked with this iteration'''
<p> </p>
<bugzilla>
{
        "product":["Loop"],
        "include_fields":"id, summary, status, assigned_to, cf_fx_points",
        "cf_fx_iteration":"40.2 - 27 Apr"
 
}
</bugzilla>
 
<p> </p>
====Iteration 40.1 (through April 13)====
* Context work:
**  Client-end: Learning some js code that was anticipated does not work how we need.  Working with desktop folks on options to resolve or implement new.
**  Server side updated [https://bugzilla.mozilla.org/show_bug.cgi?id=1141296 Bug 1141105 for Context], found issues in this iteration - next iteration. 
** [https://wiki.mozilla.org/Loop/Architecture/Context Preliminary design for encrypted room context] (name, description, etc).  This encryption work will enable future features.
* Continuing CSS clean-up in SDK and how that impacts Hello code today - continued into next iteration based on priorities
* Technical estimates/break-down for Link-clicker and in-conversation chat (not work - just working out if there are any unanswered questions)
* Share Plane was backed out of 39 - fixed test and re-landing for uplift to 39.


'''All bugs in this Release'''
<p> </p>
<p> </p>
<bugzilla>
<bugzilla>
{
{
         "product":["Loop"],  
         "product":["Loop"],  
        "bug_status":"RESOLVED",
         "include_fields":"id, summary, status, assigned_to, cf_fx_points",
         "include_fields":"id, summary, status, assigned_to, cf_fx_points",
         "cf_fx_iteration":"40.1 - 13 Apr"
         "target_milestone":"mozilla39"


}
}
Line 132: Line 113:
<p> </p>
<p> </p>


====Release 39 (ended March 30)====
====Firefox Release 39 (ended March 30)====
The Fx39 Release is only in Nightly for 5 weeks (normally 6) - ending on March 30th.
The Fx39 Release is only in Nightly for 5 weeks (normally 6) - ending on March 30th.
* Context work started in this release.  This work required implementing a changes across many systems: client front-end code, Link clicker, UX changes in both, [https://bugzilla.mozilla.org/show_bug.cgi?id=1132293 FxA Server (Bug 1132293)], and [https://bugzilla.mozilla.org/show_bug.cgi?id=1141105 Server work (Bug 1141105)].  Changes that touch multiple systems add integration cost/risk and testing complexity.
* Context work started in this release.  This work required implementing a changes across many systems: client front-end code, Link clicker, UX changes in both, [https://bugzilla.mozilla.org/show_bug.cgi?id=1132293 FxA Server (Bug 1132293)], and [https://bugzilla.mozilla.org/show_bug.cgi?id=1141105 Server work (Bug 1141105)].  Changes that touch multiple systems add integration cost/risk and testing complexity.
Line 155: Line 136:
</bugzilla>
</bugzilla>


====Release 38 (ended Feb 23rd)====
====Firefox Release 38 (ended Feb 23rd)====
* '''Firefox Release 38 Goal:'''
* '''Firefox Release 38 Goal:'''
** Fx38 goal is to break down Screen Sharing - and work to implement.  Pref-off version of screen sharing (loop.screenshare.enabled), with the Windows only sharing available early Feb. Tab sharing and Active Tab changing preparation work continued into Fx39 and was uplifted back to Fx38.  Tokbox delivered an SDK change needed to enable Tab Sharing.   
** Fx38 goal is to break down Screen Sharing - and work to implement.  Pref-off version of screen sharing (loop.screenshare.enabled), with the Windows only sharing available early Feb. Tab sharing and Active Tab changing preparation work continued into Fx39 and was uplifted back to Fx38.  Tokbox delivered an SDK change needed to enable Tab Sharing.   
Sescalante
Confirmed users
1,094

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1075070"