@Link to the recording:

https://ubc.zoom.us/rec/share/CD3_PxT4yQTy1v5x6qnjFmBz_zCeUFvUTkGWjYQPJE2gibZpEBi56NkSqoFvsOwf.IE9LI2NxOVBfofv8

Passcode: .^nhu8t#

Themes and priorities for this sprint: 

1. Data policy caching and release:

   1. LF-4240 - Getting issue details... STATUS

   2. /wiki/spaces/LITEFARM/pages/1554317313

2. Wrapping up the user story (maybe < 24 pts left?):

   1. LF-4213 - Getting issue details... STATUS

3. LF-4237 - Getting issue details... STATUS

4. Animals release scope bugs:

   1. LF-4226 - Getting issue details... STATUS

   2. LF-4212 - Getting issue details... STATUS

   3. LF-4222 - Getting issue details... STATUS

   4. LF-4238 - Getting issue details... STATUS

   5. LF-3884 - Getting issue details... STATUS

   6. LF-3606 - Getting issue details... STATUS

5. LF-4150 - Getting issue details... STATUS

6. Other Bugs Available:

   1. User can edit an already deleted expense or revenue.

   2. An assignee of the task is not notified that the task has been abandoned as a part of the Crop plan.

   3. Delete task clickable area is too large.

   4. Can't open the water calculator for a wild crop when the method of measurement is Depth

Reading for this sprint

Intro reads:

• Getting started! [10 minutes]

• Tips and tricks [5 minutes]

• Intro to the LiteFarm app [20 minutes /w videos]

• A brief tour of the codebase and tech stack [5 minutes]

• Source control and the developer’s workflow [5 minutes]

Animals specific reads:

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

• /wiki/spaces/LITEFARM/pages/822018049 [10 minutes]

• /wiki/spaces/LITEFARM/pages/1368227863 [10 minutes]

• /wiki/spaces/LITEFARM/pages/1378910214 [15 minutes]

• /wiki/spaces/LITEFARM/pages/1309999105 [10 minutes]

• /wiki/spaces/LITEFARM/pages/1404567587 [reference]

• /wiki/spaces/LITEFARM/pages/1394835499 [5 minutes, reference]

• /wiki/spaces/LITEFARM/pages/1428750337 [completed]

Forward-looking reads:

• Soil Health V1

• FY2025

What’s the definition of done for a story? 

• Code

• Language tags - (run pnpm i18n script in /webapp )

  • If En copy changes on a ticket please set all the non-En tags to “MISSING”

  • Es version of the language tag as “MISSING”

  • Pt version of the language tag as “MISSING”

  • Fr version of the language tag as “MISSING”

• Unit testing

• Check in with Loic Sans if there’s a visual component to the story

• Open up a PR, and leave it unassigned. Two reviewers 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

• User stories with UX/UI component: Passes validation with Loic Sans

Team availability

S89 runs from … to …

Days in sprint: 10