While it appears to me our relationship is working well so far, I still have a few concerns, and this seems an ideal time to make sure that we're aligned:
- I understand the dotnet LTS period is still only three years; we're up to fifteen (with ESM Legacy) and I wouldn't be surprised if we'll extend it further when customers point to a big sack of cash. If the dotnet ecosystem runs like Perl, where future versions almost always support old code with high fidelity and low stress, maybe that's fine. If the dotnet ecosystem runs like Python, where future versions are guaranteed to break existing code, such short lifespans might discourage adoption. I don't see the dotnet situation explained on https://documentation.ubuntu.com/project/search/?q=dotnet&check_keywords=yes&area=default -- the links on https://bugs.launchpad.net/ubuntu/+source/dotnet6/+bug/2023531/comments/10 are dead now and the content didn't appear to survive. - To the best of my knowledge, we don't have any local dotnet experts to help with triage, backporting, testing, etc. It seems that we've gotten along alright without so far but as we're only two years after the dotnet6 MIR conversation, perhaps that's because we haven't actually been tested yet. Is our toolchains team looking to bring on a dotnet expert? Is the security engineering team looking to bring on a dotnet expert? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2134482 Title: [MIR] dotnet10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dotnet10/+bug/2134482/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
