I am using OpenTelemetry for a long time for my tracing-related solutions, but now I want to also try logging and metrics support. As I am able to see both are in development and not released yet, so are there any plans to release for a stable version?
It's not 100% clear what release is in question but generally there are specification releases and then there are releases in specific implementations of the specification (.NET, Go, Java, ...). In another dimension we have parts of the specification (e.g. API and SDK), they have their own releases and timelines.
You can see the general status on GitHub and - more succinctly - on the OpenTelemetry web here.
As of now (Feb 14 2022), metrics are actually quite stable:
Related
The Spring Framework differentiates between actively supported versions, versions that are "not actively supported anymore", and versions that reached end-of-life (EOL). Indeed for the 5.0 & 5.1 line, there have been no more releases after the announced "no--more-support" date of December 2020.
So what's the difference between "no active support" and EOL? Will e.g. libraries be updated if there's a CVE?
Similarly, Spring Boot differentiates between EOL & end of OSS support. While it claims that e.g. the 2.2.x line has OSS support until October 2020 and reaches EOL July 2021, releases have been made until January 2021, but none after that.
So what exactly happens in the time after OSS support has ended and EOL is reached? What can one expect here?
Both uses the same concept. EOL means that you will not get any patches, help or anything in any form for those versions.
End of OSS support and "no--more-support" means that you would get security patches as well as "severe" bugs up to EOL date.
In my experience, there has been some security updates for the versions between "end-of-support" and EOL but I do not recall a patch for a bug in any.
So, what it means is that, EOL versions in production should definitively be upgraded but you can wait a but for end-of-support. But, I would always recommend upgrading at a faster pace than that. If I do not need/want the newer features, I usually wait for x.x.1 but upgrade at that point - Spring Boot might be a little longer if you have dependencies that take some time to be compatible. i.e. Tanzu Application Service is still not updated for Spring Boot 2.5 - easiest way to check it out is through start.spring.io
As far as I understand the main difference is.
OSS = Open source support - eg. you get support through github issues until that date.
EOL = End of life - even if you bought a subscription for commercial support through VMware (which is the company behind spring) for spring, you wont get any more support for this version after that date. So no security fixes or patches wont be delivered anymore.
So EOL is more critically and even important for business which bought commercial support for longer use of that particular version, whereas OSS end is relevant for most of the users.
You already linked the relevant parts - Spring Boot Support Policy
Commercial support is also available from VMware which offers an extended support period.
in contrast to
Spring Boot releases are marked as "end of life" when they are no longer supported or released in any form.
To answer your question for what you can expect after end of OSS. You most likekly still get security issues fixed but no support (except maybe commercial support) when you run into issues.
I am trying to find the FHIR 5.0 specifications and saw that some people seem to be using the FHIR v5.0 server already. According to the official FHIR blog, the specification was supposed to be released in the 3rd quarter of this year (of course COVID could have slowed this down). Could someone point me in the right direction please?
5.0 is in development and is scheduled to start balloting in May 2021. It's not likely to publish as a final 'official' release until Q2 2022. However, there's a "continuous integration build" that shows what the current proposed content for R5 is hosted here: http://build.fhir.org. As well, we produce snapshots of the draft R5 release for connectathons and other purposes so that there's a semi-stable release people can write code against when testing for connectathon.
The current timeline has indeed been impacted by COVID, but it's also been impacted by the appetite of the community for a new release and the ever increasing amount of work involved in producing a new release.
I am new to ODL. I'm using Northbound Networks ZodiacFX switches to learn with.
All the tutorials I read are written on the basis that l2switch is up and working. Without this working I have to manually build all flow table entries to allow basic switch connectivity.
1) What versions of ODL have this feature available
2) Why was proactive l2 switch programming feature removed from ODL?
Thank you.
l2switch was removed in Fluorine, so any version before that (Oxygen would be
the most recent) should have l2switch.
It was removed because the project no longer had an active community. It would
be welcome to revive if there were contributors willing to do the work.
We are going to run Cobalt on our device, and consider to the stability for partners' development.
We'd like to know...
The official version that Cobalt recommends.
Would Cobalt have a regular official version released? If the answer is yes, may I know the period of the release?
It would be great to know this information for partners preparing the environment for the future development.
Thank you.
The master branch at https://cobalt.googlesource.com/cobalt/+/master/ will always stay close to the internal development trunk. It will be a moving target in terms of stability, but will also see features first.
Release branches are sequentially named, COBALT_2, COBALT_3, and so on. They are named on when they branch, not when they stabilize, but in general it will be safest to port and release off of the latest stable release branch. These branches have gone through testing and released on one or more real production platforms.
Since this is still early days, there isn't a regular release schedule yet, but it is being worked towards. There will be more details on that when plans are finalized.
I have seen that yesterday Web API RTM has been released by Microsoft.
However I can't seem to find any log about what has changed from RC to RTM and any tips on what has changed.
We have a service that's ready for production next week, and I am not sure whether to roll with RC or upgrade to RTM this late in the project. What value does it add?
Thanks
Ubal
The official release notes can be found here at www.asp.net.
As #Aliostad kindly mentioned, I wrote an overview post highlighting what's changing and including some code samples and other references.
Henrik also wrote a nice overview post - and that one's also focused on the preview for the out-of-band functionalities available as NuGet packages (OData, tracing, Help page, and a formatting library for Win8).
If you ask whether you should upgrade - obviously yes. There aren't many breaking changes so it should be rather painless, and you get a mature, production-deployable product. It's well worth it imho.