From 8139c59c54becc8e5453df1dfe439398365425ab Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Fri, 16 Feb 2024 09:41:53 -0700 Subject: [PATCH 1/4] Added info on breaking changes to release notes for 1.6.0 --- docs/Release_notes.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/Release_notes.md b/docs/Release_notes.md index 4af9665..f5425c8 100644 --- a/docs/Release_notes.md +++ b/docs/Release_notes.md @@ -19,6 +19,9 @@ Known Issues: - The do_kafka_test.sh script in the project's root directory is currently not running successfully. The issue is being investigated and will be addressed in a future update. - According to Valgrind, a minor memory leak has been detected. The development team is aware of this and is actively working on resolving it. +Breaking Changes +- Users should note that due to the switch to J2735 2020, TIMs conforming to J2735 2016 will no longer be encoded/decoded correctly. This is due to the fact that the J2735 2020 standard has renamed some fields for TIMs. Users should ensure that their TIMs are updated to conform to the J2735 2020 standard. + Version 1.5.0, released November 2023 ---------------------------------------- From 9292f5a9927bcce844c04c7fa11fd3e9598552b8 Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Fri, 16 Feb 2024 10:45:16 -0700 Subject: [PATCH 2/4] Improved clarity in breaking changes section of 1.6.0 release notes --- docs/Release_notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Release_notes.md b/docs/Release_notes.md index f5425c8..66012ab 100644 --- a/docs/Release_notes.md +++ b/docs/Release_notes.md @@ -20,7 +20,7 @@ Known Issues: - According to Valgrind, a minor memory leak has been detected. The development team is aware of this and is actively working on resolving it. Breaking Changes -- Users should note that due to the switch to J2735 2020, TIMs conforming to J2735 2016 will no longer be encoded/decoded correctly. This is due to the fact that the J2735 2020 standard has renamed some fields for TIMs. Users should ensure that their TIMs are updated to conform to the J2735 2020 standard. +- Users should note that due to the switch to J2735 2020, TIMs conforming to J2735 2016 will no longer be processed successfully. This is due to the fact that the J2735 2020 standard has renamed some fields for TIMs. The corresponding updates in the 1.6.0 update for the ODE handles these changes for incoming 2016 TIMs, but any outside applications will need to update their systems to handle these changes prior to forwarding 2016 TIMs to the ACM. Version 1.5.0, released November 2023 From 11e269bc13990c662be2becaf493e30ccd513c06 Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Fri, 16 Feb 2024 10:53:09 -0700 Subject: [PATCH 3/4] Added specific info on TIM field renamings to breaking changes section of 1.6.0 release notes --- docs/Release_notes.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/Release_notes.md b/docs/Release_notes.md index 66012ab..209beb3 100644 --- a/docs/Release_notes.md +++ b/docs/Release_notes.md @@ -20,7 +20,12 @@ Known Issues: - According to Valgrind, a minor memory leak has been detected. The development team is aware of this and is actively working on resolving it. Breaking Changes -- Users should note that due to the switch to J2735 2020, TIMs conforming to J2735 2016 will no longer be processed successfully. This is due to the fact that the J2735 2020 standard has renamed some fields for TIMs. The corresponding updates in the 1.6.0 update for the ODE handles these changes for incoming 2016 TIMs, but any outside applications will need to update their systems to handle these changes prior to forwarding 2016 TIMs to the ACM. +- Users should note that due to the switch to J2735 2020, TIMs conforming to J2735 2016 will no longer be processed successfully. This is due to the fact that the J2735 2020 standard has renamed some fields for TIMs. The corresponding updates in the 1.6.0 update for the ODE handles these changes for incoming 2016 TIMs, but any outside applications will need to update their systems to handle these changes prior to forwarding 2016 TIMs to the ACM. The TIM changes in J2735 2020 include the following field renamings: + - `sspTimRights` -> `notUsed` + - `sspLocationRights` -> `notUsed1` + - `sspMsgRights1` -> `notUsed2` + - `sspMsgRights2` -> `notUsed3` + - `duratonTime` -> `durationTime` Version 1.5.0, released November 2023 From 182f6d7baf3d2e7ad722c9266ba76e3fea81bd7a Mon Sep 17 00:00:00 2001 From: Daniel McCoy Stephenson Date: Fri, 23 Feb 2024 12:27:17 -0700 Subject: [PATCH 4/4] Updated breaking changes section in release notes for 2.0.0 --- docs/Release_notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Release_notes.md b/docs/Release_notes.md index b417509..6a3ee13 100644 --- a/docs/Release_notes.md +++ b/docs/Release_notes.md @@ -20,7 +20,7 @@ Known Issues: - According to Valgrind, a minor memory leak has been detected. The development team is aware of this and is actively working on resolving it. Breaking Changes -- Users should note that due to the switch to J2735 2020, TIMs conforming to J2735 2016 will no longer be processed successfully. This is due to the fact that the J2735 2020 standard has renamed some fields for TIMs. The corresponding updates in the 1.6.0 update for the ODE handles these changes for incoming 2016 TIMs, but any outside applications will need to update their systems to handle these changes prior to forwarding 2016 TIMs to the ACM. The TIM changes in J2735 2020 include the following field renamings: +- Users should note that due to the switch to J2735 2020, TIMs conforming to J2735 2016 will no longer be processed successfully. This is due to the fact that the J2735 2020 standard has renamed some fields for TIMs. The corresponding updates in the 2.0.0 release for the ODE handles these changes for incoming 2016 TIMs, but any outside applications will need to update their systems to handle these changes prior to forwarding 2016 TIMs to the ACM. The TIM changes in J2735 2020 include the following field renamings: - `sspTimRights` -> `notUsed` - `sspLocationRights` -> `notUsed1` - `sspMsgRights1` -> `notUsed2`