Sprint planning - S128

Sprint planning - S128

@Link to the recording:

https://ubc.zoom.us/rec/share/vzYxMqCdZZdn8m0MSkS60coaUpQl0woECrNVoyy1j3pJHDtOoSULvZUIzeJeLrnC.EH3tuUt7ZXmO5Pop
Passcode: M1!Y=hm5

 

Happy New Year! 2026

Themes and priorities for this sprint:

  1. Tech debt items from post-release period

    1. https://lite-farm.atlassian.net/browse/LF-4242

    2. https://lite-farm.atlassian.net/browse/LF-4971

      1. JS: investigated this yesterday with the hope of maybe being able to implement it in one go, but there’s a bit more involved than I thought. Probably want to budget one dev for ~1 sprint to do properly and test all the way through

    3. https://lite-farm.atlassian.net/browse/LF-5100

    4. https://lite-farm.atlassian.net/browse/LF-5102

  2. (?? TBD) -- Getting the TAPE survey into app somewhere? This is for FAO demo on Wednesday Jan 14, 2026. IF this cannot be hosted on data.litefarm.org (preferred), we will need it on beta.litefarm.org and will also need:

    1. A suitable entry point + minimal view to show the survey (Loïc)

    2. A way to show the spider-web charts that the data team has generated before… in local? (devs in communication with Riddhi)

Update: met with Riddhi in the afternoon; all good to implement the survey and the “analysis” (it’s trivial) to show the Radar charts in app.

  1. If not implementing TAPE, beginning our new epic: https://lite-farm.atlassian.net/browse/LF-4949

    1. https://lite-farm.atlassian.net/browse/LF-4950

    2. https://lite-farm.atlassian.net/browse/LF-4955

 

Highest Contributor Priorities:


*Please tag dev or design on ticket if requirements are not clear or defined

 

Bug Bash Bugs

Contributors, please refer to the latest Bug Bash document:

https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/2139422721


The two tables (a UX/UI table and a bug table) list a lot of issues, not all of which were release scoped. If one of these issues that hasn’t been addressed appeals to you, please create a ticket from the table entry Table entries that were already resolved should have a linked ticket with a status of “released”. A few table entries might have tickets already, but remain in backlog (= were not picked up for release 3.9.0)

 

Other Available Bugs

Medium priority

Feature Tickets

Tech Debt

Reading for this sprint

Intro reads:

Smart Irrigation specific reads:

Other readings haven’t been significantly updated since S79. However, they’re listed below from most high level to most detailed:

Forward-looking reads:

What’s the definition of done for a story? 

  • Code

  • Note update language requirements:

    • Add string to en

    • Mark your PR with the “new translations” tag

    • The CrowdIn GitHub automations will do the rest

  • Unit testing

  • Open up a PR, and leave it unassigned. A reviewer from the core team will be automatically added. Core team to incorporate feedback given during peer review.

  • Passes peer review x 1

    • Reviewer will be auto-added

  • Merged

  • Passes verification

Team availability

This sprint runs from … to …

Tuesday, January 6, 2026

Wednesday, January 14, 2026

Days in sprint: 7

Person

Days in sprint

Notes

@Sayaka Ono

3

Back from vacation Mon Jan 12

@Joyce Sato-Reinhold

7

 

@Denis Dovganyuk

???

Baby due!!

@Divya Chayanam

6

OOO Fridays

@Loic Sans

5

Tue - Thu

@Duncan Brain

7

Volunteering now: Should be in every day at least a little bit. OOO: Jan 17-24

 

 

 

Contributors