## Release-only sprint

- Something new
- Pause new development (release is team-wide focus)
- To start one week, whole team
- Later on some team members, faster and faster overall
- Release driver will be the primary coordinator (not all the activities are done by that person)

## Goal

More first aid:

- Get out "ready features" for develop
- Remove draft mapping model into feature branch
- Move forward all loose ends and enhancements in `develop` (unless otherwise discussed, team will review together)
- Work with A.J. to update 1.1.0 milestone in GitHub
- [Follow release guidance and release it](https://github.com/usnistgov/OSCAL/wiki/OSCAL-Release-Checklist)!
- Make announcement and "release" migrated website (#1802)

## Sprint Details

This special release sprint is from 11-25 July 2023. Intent of this sprint by 25 July 2023:

- Release a new minor release by 25 July 2023
- Migrate website by 25 July 2023

Release driver for this sprint: Nikita

### Leave or other priorities

- AJ has 65-70% focus has another project, managing SURF student, and potential IETF travel and standards work
- Chris will be taking some leave on/after July 27. Shouldn't impact unless we extend on anything.
- Nikita will be taking Wednesday the 12th off.
- DC 16-18 hours
- Michaela - makes this release priority #1 - pls ping/text me on 202-308-0890 IF not responding fast (1hr or so), but has OSCAL mini workshop CSRC updates (video/transcripts processing, a cloud security book chapter too close to deadline)

### [B]lockers, [C]oncerns, [R]isks

- [R] how can we support the community in a website migration (site content and artifacts) and announce?
- Brief community?
- Pre-stage artifacts and "back-port" release artifacts for previous 1.0.0-1.0.6 releases
- [C] Do we maintain old reference for a short-time or do we immediately cut to new reference site at the time of release?

### Action Items