## 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
Last changed by  
 
Alexander Stein
73

Read more

oscal-cli 1.0.3 Release Brief

oscal-cli 1.0.2 is a patch release with improvements and changes that are backwards compatible, specifically updating liboscal-java and metaschema-framework dependencies to make use of the OSCAL v1.1.1 models and the underlying use of the Metaschema Framework.

2/2/2024
liboscal-java 3.0.3 Release Brief

oscal-cli 1.0.3 is a patch release with improvements and changes that are backwards compatible, specifically updating liboscal-java and metaschema-framework dependencies to make use of the OSCAL v1.1.2 models and the underlying use of the Metaschema Framework. This release also fixes a bug to properly reference embeeded resource files in the release.

2/1/2024
Demo Video script for metaschema-cli

Download from Maven

1/22/2024
Value stream issue management for usnistgov/OSCAL#1688

We propose in this draft document with a non-exhaustive list of value streams. A value stream is a thematic collection of work items, varying in scope of work by quantity or quality (large epics to small issues), but still relate to the same theme in that work. There are different kinds of work items, with some nested like epics with user stories within them. It is counter-intuitive to talk an epic nested with epics, so we will label each one as a value stream. For organizational purposes, we organize the value streams grouped by high-level use cases in OSCAL. This grouping may be beneifical to link the resulting value of work completed in a value stream to a downstream developer making OSCAL-enabled tooling.

1/5/2024
Read more from Alexander Stein
Published on HackMD