Milestones
List view
- No due date•3/4 issues closed
Complete the planned breaking changes in JiraPS 3.0.0 before freezing the public API, so they do not force another major release shortly afterward. ## P0: required v3 work 1. #194: finish the session/server API, named per-call connection selection, isolated authentication/cache state and configuration migration. 2. #681: finish C# public return objects, stable nested models and intended typed consuming parameters. #612 is already merged; complete the remaining gaps. 3. #651: return all Cloud create-metadata fields/pages, require nonempty output assertions and preserve Data Center behavior. 4. #604: preserve PowerShell 7 HTTP errors when ErrorDetails is absent, with Windows PowerShell 5.1 compatibility. 5. #648: replace silent parameter-type assertions and verify the final public signatures. 6. #674: fail when required Cloud/Data Center integration cases are missing or unexpectedly skipped. Run #706, the licensing disposition and final evidence work, in parallel from the start because contributor response time is external. Session and C# contract work comes before the final signature, migration-help and release-candidate validation sweep. Bounded independent fixes can proceed in parallel. ## P1: supporting contract decisions required before v3 freezes - #45, #130 and #196: settle server selection, configuration and ServerInfo requirements under #194. - #613: decide which known string-set fields use enums and implement the chosen public contract. - #614: settle User constructor and Cloud/Data Center identity behavior. Preserve the explicit assignee switches rather than restoring obsolete magic-string proposals. - #174: settle comment/worklog visibility models and consuming parameters, with compatibility aliases where useful. These six issues are part of v3. Implement the intended breaking changes now. Document any deliberate decision to retain an extensible representation. AtlassianPS/AtlassianPS#4 coordinates the authentication direction. Other modules can adopt the completed session contract after JiraPS v3; their migration does not block this release. ## Release exit conditions - Resolve all seven P0 workstreams and the six supporting contract issues. - Verify migration guidance and packaged cmdlet help against the final session and C# contracts. - Pass build/tests, Windows PowerShell 5.1/PowerShell 7 CI and full Cloud/Data Center integration on the exact candidate commit. Review required cases and deployment-specific skips. - Review the exact release artifact and existing release controls. AtlassianPS/AtlassianPS#13 tracks CD evidence. OAuth, additive cmdlets and internal optimizations can follow in compatible 3.x releases. Broader organization cleanup and other-module releases are outside this milestone. Keep JIRAPS_CD_ENABLED=false. Preparing or publishing JiraPS 3.0.0 requires fresh explicit maintainer authorization naming the repository and version, followed by the existing gated release procedure. This milestone does not authorize publication.
No due date•11/22 issues closed