Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Facilities Draft Sprint 104 Plan #17076

Closed
xiongjaneg opened this issue Jan 29, 2024 · 4 comments
Closed

Facilities Draft Sprint 104 Plan #17076

xiongjaneg opened this issue Jan 29, 2024 · 4 comments
Labels
Epic Issue type Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide

Comments

@xiongjaneg
Copy link
Contributor

xiongjaneg commented Jan 29, 2024

Schedule Notes

  • Alexis out 2/14
  • Jill out 2/12-2/16
  • Jane out 2/16
  • Christian out 2/16 to 2/21
  • Washington's Birthday/Presidents Day
    • Friends holiday
    • Not an A1M holiday
    • A6 holiday
    • Not a Civic Actions holiday
  • Design system update by 4/19

Sprint Priorities 🎯

At the end of this sprint, what do we want to have accomplished/delivered?

Tickets for top priority:

Other Sprint Work

UX

Drupal

Front end

@xiongjaneg xiongjaneg added Needs refining Issue status Facilities Facilities products (VAMC, Vet Center, etc) Epic Issue type labels Jan 29, 2024
@mmiddaugh
Copy link
Contributor

mmiddaugh commented Feb 13, 2024

Front end: Vet Center unpublished services should not be showing on VA.gov #16362
Drupal: Review release notes and upgrade Upgrade Address module in an integration branch #14083

From the Design system: ON 4/19, ALL V1 COMPONENTS WILL BE OFFICIALLY RETIRED AND NO LONGER AVAILABLE FOR USE. TEAMS THAT HAVE CHOSEN TO OPT OUT OF V3 COMPONENTS NOW WILL NEED TO PLAN MIGRATION TO V3 PRIOR TO 4/19.

  • It's possible custom components could break with font family size increase when the "typography update" occurs, no known date but expected in the next month.

@xiongjaneg
Copy link
Contributor Author

For components using classes but not a link component (may not have a V3 component), how will these be affected?

Not all V1 components have a V3 equivalent. In that case, they may continue to be excluded from this update.

@swirtSJW
Copy link
Contributor

@xiongjaneg I created this ticket #17241 which is a blocker for service location launch.

@xiongjaneg
Copy link
Contributor Author

@swirtSJW You're a mindreader. I was just looking for this info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Issue type Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide
Projects
None yet
Development

No branches or pull requests

4 participants