@Link to the recording:

https://ubc.zoom.us/rec/share/_pwQ_Y8A2ZqhG2pqRJh5SaADM_3bmVGLD7KbhJ82Et-oqrS-_1i1gkjul8YFAxrg.DPb31ZPc_4f4CivR

Passcode: tX7!e6RZ

Themes and priorities for this sprint:

• Synching up Smart Irrigation (Irrigation Prescriptions) with Ensemble

• Soil sampling researchers flow

• Preparing for release 3.8.0

Highest Core Team Priorities

Onto preparing for the next release! 3.8.0 and the wrap-up of smart irrigation:

• Should be able to check farm setups with Lewis / Farming Smarter on MONDAY

• Ensemble to also be meeting with Lewis this week about pivot properties

• ESci still to add VRIs… should we schedule a bug bash for the end of this sprint, or is that too optimistic?

Follow-ups from last sprint:

• Release notes?

  • One big set of release notes for 3.7.7 & 3.8.0 (was tagged for Loïc and @Denis Dovganyuk last Sprint) @Divya Chayanam to follow-up and possibly wrap up

• Translations – Hindi & German coming in?

  • German will be re-contacted; @Divya Chayanam; Divya also to do Hindi

• Consent

  • @Joyce Sato-Reinhold and @Divya Chayanam to connect about this

  • Update: will not be necessary for this release

Irrigation Prescriptions https://lite-farm.atlassian.net/browse/LF-4759

• S115 included meeting with Ensemble and updates for these actual Ensemble endpoints:

  • https://lite-farm.atlassian.net/browse/LF-4766

    • Should be testable on beta cronjob today, but structure of this will change further to handle the two locations / two crops on one pivot situation

  • https://lite-farm.atlassian.net/browse/LF-4767

    • Mostly complete, just needs date handling fixed up (in communication with Ensemble about this), and the locations change that will come in next week

  • https://lite-farm.atlassian.net/browse/LF-4788

    • Needs quite a few properties hashed out with Ensemble; in communication

Soil sample researcher’s flow – NOT required for Release 3.8.0 (according to last Sprint Planning’s discussion), but we could look at it while we wait for Ensemble + Smart Irrigation

• https://lite-farm.atlassian.net/browse/LF-4827

  • @Divya Chayanam to get in touch with Jessica

  • @Joyce Sato-Reinhold to contact Riddhi / data team about database format of results → DONE. Will put notes in the Jira tickets

Take a look and discuss this as a backup task:

• https://lite-farm.atlassian.net/browse/LF-4737

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

IN PROGRESS (TECH DEBT)

• https://lite-farm.atlassian.net/browse/LF-4657

• https://lite-farm.atlassian.net/browse/LF-4708

AVAILABLE BUGS

High Priority

• https://lite-farm.atlassian.net/browse/LF-4887

• https://lite-farm.atlassian.net/browse/LF-4843

Medium priority

• https://lite-farm.atlassian.net/browse/LF-4881

• https://lite-farm.atlassian.net/browse/LF-4716

• (Sizeable task, relating to persisted form data across app) https://lite-farm.atlassian.net/browse/LF-4614

• https://lite-farm.atlassian.net/browse/LF-4741
  
  

Lower priority

• https://lite-farm.atlassian.net/browse/LF-4605

• https://lite-farm.atlassian.net/browse/LF-4727

Reading for this sprint

Intro reads:

• Getting started! [10 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]

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:

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1483472927 -[2min]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1694629889 - [9min]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1185611781 - [7min]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1202290689 -[6min]

• https://lite-farm.atlassian.net/wiki/spaces/LITEFARM/pages/1732935690 - [6min]

Forward-looking reads:

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

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. Two reviewers from the core team will be automatically added. Core team to incorporate feedback given during peer review.

• Passes peer review x 2

  • Reviewer will be auto-added

• Merged

• Passes verification

Team availability

S114 runs from … to …

Days in sprint: 10