Dev Team Innovation and Planning (FY24 Q4)

[nathankota]

Benefit

The final sprint of the quarter is meant to be an Innovation and Planning (IP) Iteration. Benefits include:

• Allow time for Innovation
• Dedicate time to PI Events (I&A and PI planning)
• Integrate the Complete Solution (presentation of work of all teams on the train)
• Advance Development Infrastructure
• Enable Continuous Learning

Possible tasks include:

• Pay down technical debt
  • app and data dependencies and updates
  • updating CIs
• Other modernization tasks
• Cloud migration
• "Work on whatever with whomever"
• Alignment of best practices

Acceptance Criteria

Possible Tasks

• Survey app users for their input on changes/improvements raster#169
• Consider https://github.com/step-security/harden-runner this quarter or another
• Revisit the reactfire npm conflicts
• Some action workflows are not completing since their required checks aren’t running
• Push swapper to pypi and automate builds Pypi swapper#19
• Update: black, ruff, palletjack skid#8
• Migrate to actions/create-github-app-token
• Migrate to Artifact Registry
  • geocode-job
  • unclaimed property
  • roadkill
  • masquerade
  • parole
  • [ ] cambiador
• Palletjack: Palletjack Updates #274
• Masquerade:
  • Masquerade Enhancements #91
  • Masquerade - Search by Coordinates #281
• Upgrade Pro version on Forklift machine
• Skid readme's
  • https://github.com/agrc/uorg-skid/issues/3
  • Update readme dabs-skid#4
  • update readme wmrc-skid#33
  • Update readme broadband-speedtest-skid#5
• Bump agrc/get-next-version-action to Node JS v20
• Bump agrc/release-composite-action to Node JS v20
• Release pipeline: Separate deployments releases by moving them to a separate workflow that is triggered by published releases. This would make it easier to rerun them if there was an issue with the deploy.

Notes

No response

Risks

No response

Issue Reference

refs #311

[nathankota]

Copied from #311, before moving more of the Acceptance Criteria tasks to here, and closing 311.

[nathankota]

Sprint 6

• Survey app users for their input on changes/improvements raster#169

[steveoh]

Sprint 6 Notes (Steve)

• Atlas improvements
  • Started to replace reactfire from atlas
  • Started to incorporate design system elements
  • Started to restructure the UI
• Design system improvements
  • Evaluated building blocks for design system and chose to migrate to react-aria
  • Created sherlock component
  • Created Header component
  • Created Footer component
  • Created Social component
  • Started Button component
  • Started Input component
  • Started Dartboard component building on Button and Inputs. Stuck on react hook form integration.
• API Client improvements
  • Migrated to an improved build system with vite
  • Created universal builds for intel and arm based systems
  • Added a beta channel for testing new features
• gis.utah.gov improvements
  • Evaluated broken link checker and created list of links to triage
• UIC improvements After finding out UIC was in production
  • Fixed a bug with admin notifications
  • Added a link to a help doc that was created
  • Fixed a bug with database columns not matching input size limits

[stdavis]

Sprint 6 Notes (Scott)

• Release Pipeline
  Investigated semantic-release as an alternative to release-please. Ended up coming back to release-please but got some good ideas for enhancing our pipeline.

  • fix: more consistent subsequent prerelease versions get-next-version-action#154
  • upstream bug in release-please

• Built https://github.com/agrc/release-issue-notifications-action
  The idea for this came from semantic-release.

Helped with universal builds and beta channel for API Client