Feature #6187
closed
Update titan.core to 9.0.0 in osmocom repositories
Added by pespin 8 months ago.
Updated 8 months ago.
Description
AFAIK we now ship titan 8.3.0, bit 9.0.0 is already available upstream with several bug fixes.
We may want to update it to 9.0.0.
- Related to Feature #5323: Add docker image containing titan.core master added
I'm fine with that. Let's see if fixeria or laforge have any concern.
I didn't look at the release notes nor commit history in detail. It may make sense to have a look and see if there are fixes for new regressions after 9.0.0.
I don't have any specific remarks. In general it is good to follow upstream unless there are known significant regressions affecting our test suites
pespin wrote in #note-3:
I'm fine with that. Let's see if fixeria or laforge have any concern.
I didn't look at the release notes nor commit history in detail. It may make sense to have a look and see if there are fixes for new regressions after 9.0.0.
Even though the '9.0.0' is a major release, it's not that far away from the '8.3.0' (see git log --oneline 9.0.0 ^8.3.0
): only 44 commits and mostly ASN.1 related patches (adding PER support, incomplete yet). I have the 9.0.0 installed since I migrated to a new laptop and so far was mostly running ttcn3-bts-test. No regressions observed. I am fine with upgrading the testsuite infra to use it, no concerns. But I don't see any major benefits, so maybe reduce to Low prio?
After writing the above part, I took a closer look and found out that several of your bug reports have been fixed in this release:
https://gitlab.eclipse.org/eclipse/titan/titan.core/-/issues/636
https://gitlab.eclipse.org/eclipse/titan/titan.core/-/issues/690
- Status changed from New to Resolved
- Assignee set to osmith
- % Done changed from 0 to 100
Also available in: Atom
PDF