I have gitlab integration and I am trying to configure release versions. I used sentry-cli to create release and associate commits. I used sentry-cli releases propose-version to get SHA-1 and set it like release version. My version in SDK must me equal this SHA-1 return or I can use any custom version name?
I figured it out. Version set from sentry-cli and version in sdk must be equal. That allows you to link the error with the release.
Related
How do you configure Xcode (13.2) to add a dependency on a pre-release version of a package?
For example, right now Sparkle has a 2.1.0-beta.2 release which I would like to test in my app.
More accurately stated, I would like to accept 2.1.0-beta.x up to and including the full release of 2.1.0 and I'd like Xcode's "Update to latest package versions" to find the new releases for me without me changing anything in the configuration (eg like you can do with npm).
I can't find any obvious way to achieve this using the Xcode UI. If indeed you can't, is there a way to specify this version range by editing a config directly?
As mentioned here, 2.1.0-beta.2 < 2.1.0, which is why I have tried 2.0.0 in the screenshot.
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.
I just upgraded from SonarQube 6.1 to 6.7.7. For SonarJava, it automatically installed 4.15.0.12310 (it was 4.10.0.10260 before). In the Marketplace, when I hover over the available versions from 5.0-5.13, it says “Incompatible”. When I hover over 5.13.1+, it says “Requires system update”. What does it mean for it to be incompatible if it doesn’t require a system update?
I am seeing this with various other plugins as well, such as SonarPython, which had 1.8 automatically installed. I had to manually install 1.9.1 in order to get this bug fix (which is why I originally upgraded the server): https://community.sonarsource.com/t/python-s1481-code-smell-unused-local-variables-should-be-removed-false-positive-with-string-interpolation/8961
I could manually install newer versions of other plugins as well, but I don’t know if that’s safe.
I also can’t find an official plugin compatibility matrix, since this only shows 7.9+: https://docs.sonarqube.org/latest/instance-administration/plugin-version-matrix/
Incompatible means that the plugin does not work with the version of SonarQube you have installed.
An example of an incompatible plugin would be one where the plugin relied on an API that was removed in your current SonarQube version. You may be able to use that version of the plugin if you downgraded your SonarQube instance to a previous version.
Requires system update means you need to upgrade SonarQube in order to install the plugin.
For what it's worth, the states as described by the API documentation are:
Update status values are:
COMPATIBLE: plugin is compatible with current SonarQube instance.
INCOMPATIBLE: plugin is not compatible with current SonarQube instance.
REQUIRES_SYSTEM_UPGRADE: plugin requires SonarQube to be upgraded before being installed.
DEPS_REQUIRE_SYSTEM_UPGRADE: at least one plugin on which the plugin is dependent requires SonarQube to be upgraded.
I have a requirement that i need to update the build version numbers of old releases. Currently build version number starts with '1'. But i need to update to some number for old releases. I am using teamcity 7.1.5 (build 24400). Is this possible to update the old version number like 1.0.23568 to 5.0.23568?
http://www.springsource.org/downloads/sts-ggts
I am trying to download new STS tool. On the above site I find
Milestone Version and Release Version. Can anyone tell me what these terms mean? Which is Users version to be used and is completely developed and not under-development?
The release version is the one you want, "release" means it's considered to be done and ready for the public. "Milestone" means it's a stable checkpoint made available for community developers to test. You'd pick the milestone one if there are new features or bugfixes you want to try out that haven't been included in a release yet.