Plan Obligation Milestones for 2025 #615
Comments
nils-work
added
the
Documentation
|
Following the Y24 convention (typically the second Monday of every second month, from March-November) in the Obligation Dates Schedule, Y25+ dates could be specified as follows (in bold) -
Please note the detail in the schedule section, including:
|
nils-work
added
the
Non-breaking change
|
We discussed this issue in the first meeting for Maintenance Iteration 19. Instead of looking across the next three years, we are consulting on feedback specifically for 2025 in this iteration. |
|
The focus for MI19 consultation is the schedule of 2025 dates to be added to the Obligation Dates Schedule table in the next Standards version.
|
nils-work
added
the
Proposal made
|
The proposed change has been staged for review. |
|
In today's Implementation Call it was noted that Y25 Obligation 1 (10th March 2025) is a public holiday in Victoria (Labour Day). It also coincides with Adelaide Cup Day (South Australia), Canberra Day (ACT) and Eight Hours Day (Tasmania). See https://www.fairwork.gov.au/employment-conditions/public-holidays/2025-public-holidays The original purpose of selecting obligation milestone dates on the second Monday was the feedback received from Data Holders to avoid key shutdown periods and avoid mid-week releases. The feedback at the time was that a Monday obligation gave Data Holders choice to have teams deploy over the weekend (potentially reducing customer impact) and monitor on the Monday in case of rollback or hotfix. Importantly, the obligation date represents the last day to deploy compliant implementations, and the expectation is that Data Holders plan their deployments appropriately so they do not deploy at the 11th hour (which in turn increases their risk). Given that the first milestone falls on a long-weekend for many Data Holders, it is proposed the first milestone be shifted one week later to 17th March 2025. The alternative is shifting the date one week earlier to the 3rd of March 2025 however this clashes with a public holiday in Western Australia. The revised schedule below is proposed:
|
* 1.30.0 branch * Updates to base build * Update releasenotes.1.30.0.html.md * Updated release notes templates * Removed repeated object * Removed duplicate TelcoAccount schema Addresses: ConsumerDataStandardsAustralia/standards-maintenance#634 * Create clean 1.31.0 branch * Expanded nested array structure for previousDays Addresses: ConsumerDataStandardsAustralia/standards-staging#396 * Remove redundant TelcoAccount object * Update releasenotes.1.31.0.html.md * Enable generic links to schemas Addresses: ConsumerDataStandardsAustralia/standards-staging#400 * Updated Consumer Data Right link Addresses: ConsumerDataStandardsAustralia/standards-staging#402 * Updated Obligation Date Schedule Addresses: ConsumerDataStandardsAustralia/standards-maintenance#615 * Removed title text * Standards Maintenance Issue #640: Changed retirement date of Get Generic Plan Detail v2 and Get Energy Account Detail v3 to March 3rd 2025 * Standards Maintenance Issue #415: Clarified that a Token Introspection End Point response must include specific fields only for currently active tokens * Standards Maintenance Issue #415: Corrected release notes change description * Standards Maintenance Issue #415: Updated link to change in release notes * Standards Maintenance Issue #415: Fixed spelling mistake in release notes * Standards Maintenance Issue #633: Changes to CX and Security standards to clarify cdr_arrangement_id is requried for consent amendments * Standards Maintenance Issue #633: minor presentation fixes * Updated FDO table Addresses: ConsumerDataStandardsAustralia/standards-staging#377 * Presentational styling of Banking documentation Addresses: ConsumerDataStandardsAustralia/standards-staging#395 * Moved the March 2025 FDO to the 17th * Standards Maintenance Issue #640: Moved release notes entry to Introduction section * Standards Maintenance Issue #643: Allow data holders to depricate use of vulnerable TLS ciphers * Standards Maintenance Issue #415: Made the word SHALL bold * Fixed typo (#399) Addresses: ConsumerDataStandardsAustralia/standards-staging#394 * Standards Maintenance Issue #643: Fixed typo in release notes * Added MI19 DP link change log, re-ordered CRs in releasenotes * In release notes, changed link to obligation date schedule for CR 615 * Build standards version 1.31.0 for staging * Added change date in Change Log. Added None to release notes sections where there are no changes * Rebuild version 1.31.0 in preparation of publishing --------- Co-authored-by: Nils Berge <[email protected]> Co-authored-by: Hemang Rathod <[email protected]>
Description
The Milestone Dates in the Obligation Dates Schedule currently extend to 11/11/2024.
Area Affected
Obligation Dates Schedule
Change Proposed
Plan Milestone Dates for 2025 to include on the Obligation Dates Schedule.
DSB Proposed Solution
The proposed solution can be found in this comment.
The text was updated successfully, but these errors were encountered: