Boehm-gc 7.6 is on the prerelease status, When will boehm-gc 7.6 be released?
Can we use it in product now?
I can't found the release plan or any roadmap.
Thanks!
gc 7.6.2 will be released by Oct. At this moment, for production, I'd recommend to use gc 7.4.x or, better, checkout release-7_6 branch at https://github.com/ivmai/bdwgc
Related
I want to upgrade my ES cluster(current version: 7.6.2) to the latest version (7.15.2 until now)
Is it ok to upgrade directly to the latest version or should I upgrade with 2 or 3 steps on different version?
For instance, for upgrading mongo db, it should be upgraded step by step to the next version...
I just want to know what is the policy or even best practice for upgrading ES ?!?
Thanks
It's totally fine to update between minor versions (7.x -> 7.y) as well as one major version up from latest minor version (6.8 -> 7.y), see upgrading document for the details. Best of all, it can be a rolling upgrade so you can upgrade nodes in the cluster one by one without cluster downtime or data loss. Just make sure cluster health is green before moving on to the next node.
For my app i need FFmpeg, so i went to official website, for windows builds it said go here :-
https://github.com/BtbN/FFmpeg-Builds/releases/tag/autobuild-2021-01-20-13-01
But now i have a problem.
Which version of ffmpeg is newer ?
ffmpeg-N-100679 or ffmpeg-n4.3.1-29 ?
Is that "N" version unstable and "n4" version stable ?
Any help would be appreciated 🙂
Which is newer?
ffmpeg-N-100679-g24dc6d386c is newer. It is from the git master branch, and is a snapshot of the current, up-to-date FFmpeg code for the date it was released. It corresponds to commit 24dc6d386c (note I omitted the g prefix) which is from 2021-01-20.
4.3.1 is from 2020-07-11. Since new features are not backported to release versions (only certain bug fixes) it is just an extension of 4.3 which was released on 2020-06-08. The FFmpeg Download page contains the dates for releases.
So ffmpeg-N-100679-g24dc6d386c is about 7 months newer than 4.3.1.
Which do I use?
ffmpeg-N-* for general users. If you want the latest code and features. Required for anyone who wants to submit a bug report. If you experience a problem with the newest release. It is stable ~98% of the time I'd guess from using it over many years.
Release version: if you are required to stay within a certain API version. For distros, distributors, users of the FFmpeg libraries, etc.
Versions with N-xxxxx are nightly builds / snapshots and are unstable (but newer). Use them only for testing or if the last release has a bug that is already fixed and only available in the nightly.
Otherwise I recommend to use the latest release (currently 4.3.1). This is typically more stable.
GREENWICH.RELEASE was released by the beginning of this year while SR3 is recently released. Can anyone explain what service release (SR) means? Is it same as SNAPSHOT and will be changed frequently? Or are they fairly stable versions that can be used in a production environment?
An SR means Service Release (subsequent maintenance releases that come after major RELEASE), it's completely stable and can be used on production.
We would like to upgrade our Sonar setup to 6.x but waiting for LTS release. Is there any update on when Sonarqube LTS (6.x) release is scheduled?
Also, we would like to understand major differences between Sonarqube 4.5.7 & Sonarqube 6.x in terms of support for Java/maven/msbuild/fxcop versions and other major features that 4.x users should be aware of.
The release of 6.7 LTS is planned for this fall. But you cannot upgrade directly from 4.5.7 to 6.7; you must first go through the intervening (current) LTS: 5.6.6.
For a summary of the differences between 4.5.7 and 5.6.6, see this blog post. If you want more details, you should consult the release notes, as Simon noted in the comments.
When you upgrade to 5.6.6 (why not go ahead & get that out of the way?), you'll find that your custom dashboards are still there, but have been set aside in favor of a hard-coded project homepage. When you get to 6.7, you'll find that custom dashboards have been eliminated entirely, and a new projects page has been provided, as well as a reworked Measures space and countless other improvements.
Nov 2019 Update: The current LTS is now 7.9. More information about the SonarQube LTS model is available here.
My understanding is that Findbugs 3.0.0 will support analyzing Java 8 bytecode. I see that there is a beta version of it available here:
http://sourceforge.net/projects/findbugs/files/findbugs/3.0.0/
SonarQube is waiting until the final version of Findbugs 3.0.0 is released before upgrading their Java plugin to use it. This means SonarQube is unable to analyze our Java 8 projects.
Is there a target date for Findbugs 3.0.0 release or a known workaround for using the beta version of it with SonarQube?
Well, 3.0.0 RC1 is released today (25.06.2014) and we plan to release 3.0.0 final (if there will be no major regressions reported) in July.
Update: 3.0.0 is released on 06.07.2014, see https://mailman.cs.umd.edu/pipermail/findbugs-discuss/2014-July/004029.html
As per mailing list thread : https://mailman.cs.umd.edu/pipermail/findbugs-discuss/2014-May/003999.html
The release is now mainly depending on early adopters feedback.