What's the difference? is one better or are the older versions only kept for the sake of keeping?
I saw that 4.5 is no longer available.
I'm using 4.6.2, and it seems to be fine...
You can see a list of the major changes here. If you're happy with the version you're currently using, I suppose there's no hurry to upgrade though.
The GCC project generally maintains two stable release branches. Currently those branches are 4.6.x and 4.7.x.
Related
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've recently released version 4 of SBJson. This is a new major version that is not backwards compatible. Since SBJson is widely bundled by other popular libraries I renamed all the classes & enums to make sure it can be used in conjunction with prior versions.
However, I'm not sure how to best handle this situation with CocoaPods. I contributed a 4.0.0 spec to the existing SBJson specs, but I suspect it will be impossible to install version 3.2 and 4.0.0 in the same project. Do I have to clone the 4.0.0 spec into a SBJson4 (notice extra major version number in name) spec as well?
Morning.
If you want users to have both versions installed simultaneously they will probably have to be separate pods.
AFAIK you can't have one pod installed twice in a project. I don't even know how you'd get round the linker errors etc. for that to be possible!
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.
Is DWR a dead project? It does not appear to be under active development. The latest 3.0 release appears to be stalled. I'm specifically wondering if there are going to be maintenance releases of DWR 1.x or 2.x or is 3.0 is ever going to be released.
BTW. I asked this question on one of the DWR mailing lists and did not get a response.
Well, the 3.0 version is taking a while to get released, but it is nonetheless very stable.
We are using it in our production environment and we do did encounter any issue so far (2+ years in use).
Important issues on 2.0.X are fixed BTW. (seems that currently there are no major issues on 2.0.X).
BTW. I asked this question on one of the DWR mailing lists and did not get a response.
We had issues before (other version) and those were handler very quick.
Update Dec/2015: V3.0.1 released
Seems like it, I have used DWR like a year back and there is no release since then.
Their version 3 is still on RC (release candidate) and from my understanding of versioning, it is not stable or a general acceptance.
I would say move on... pass DWR. Pass Java too if you can ;)
I've been trying to build the 3.2.2 and 3.2.3 tags of WSO2 Carbon from here using Maven 2:
https://wso2.org/repos/wso2/tags/carbon/3.2.2
https://wso2.org/repos/wso2/tags/carbon/3.2.3
However, the Maven pom.xml files throughout the directory trees beneath these tags still refer to version 3.2.0 in both cases - am I missing something obvious please?
When I try and analyse the results of both the builds using our in-house tool I get identical results in the two cases (and indeed results that are identical to those for 3.2.0), which makes me think I may be building 3.2.0 repeatedly by accident.
3.2.2 and 3.2.3 are point releases and typically involves bug fixes/optimizations that do not introduce new features to the 3.2.0 release. If a particular component do not have any fixes/changes, the version still be the older version, no new version is introduced. This is how the versions are handled.
You're not missing anything. It seems they did screw up. Maybe that was their intention, but then it doesn't make any sense at all (at least for me).