Suppose I have version 1.1.0 on a NuGet server.
I then continue development and push version 1.2.0.
Then I find a bug in version 1.1.0 and want to fix this.
At this point, can I still push version 1.1.1?
There's nothing in the NuGet spec or protocol that prevents it, so it might depend on which NuGet server you're using, but I would be extremely surprised if any server forbids it because it would be so short sighted, in my opinion.
Using NuGet.Protocol on nuget.org as an example, version 4.9.3 was release in January 2019, but versions 4.8.2, 4.7.2, 4.6.3, 4.5.2, 4.4.2 and 4.3.1 were released in March, two months later.
Related
Newest available version of Tesseract is 5.x. but the latest tika is still using 4.x.
Is it possible to upgrade version of tesseractOCR in Tika?
We kept the 1.x branch alive for a year after cutting over to 2.x to
allow people time to migrate. Most of the changes in 1.x in the last
6 months or so have been security related. We will no longer support
1.x after September 30, 2022.
I've opened a ticket and PR to upgrade tesseract to 5.x in our next 2.x release -- 2.5.0.
https://issues.apache.org/jira/browse/TIKA-3860
To my knowledge, the latest non-alpha version of the #ui5/cli and #sap/ux-ui5-tooling (as of 2nd March 2022 - version 2.14.6 and 1.5.0 respectively) are the ones to use.
However, I wanted to confirm as my organisation has multiple ui5 projects and so having a standardised version of the #ui5/cli and #sap/ux-ui5-tooling dependencies could prevent issues around bugs in tooling.
If the advice is just to use the latest non-alpha version, then I just need to update the dependencies regularly.
The versions you mentioned should be your choice to use in a productive environment.
The upcoming UI5 tooling 3.0 is not.
I don't think you will achieve the same version in every app because of the lifecycle.
The packages are fast paced and when u have a stable app deployed you will not update it every month I think.
I would not invest time to find the perfect tooling version.
I'm totally confused about the release numbering Unity is using. Looking at GitHub, I see that the latest release is referred to as 'Release 17' yet the version numbers when looking at things in Package Manager look like 1.08.
Is Release 17 the same as 1.08? Could someone clarify that.
Also, I downloaded Release 17 and installed it by referencing the package.json file however, Unity show it up as 2.0.0
I hope you guys can help.
thanks
Based on Unitys docs about Versioning I would guess that the overall count of releases is 17, meaning there have been 17 public releases of the package. There is usually a change log that you can find using the package manager that goes into a little more depth for each version. I would guess that the github has more versions than the package manager as the versions released on the package manager are most likely more stable and not just hot fixes.
To summarize, they've had 17 releases, some could have been before version 1.0.0 and you mentioned that 17 is 2.0.0. It could be that 2.0.0 is not stable yet which is why you need to download it from Github to have it in the package manager. Anything prior to the first digit is a patch release version increase. So with 1.0.8, it means they're on major release 1 on patch version 8. The other reason 2.0.0 might not appear in your package manager is due to being on a non verified version of Unity for this package version or not viewing unreleased packages. It could be 2.0.0 works, but is not verified by Unity yet on your Unity version.
Currently I am using Rundeck 3.0.23-20190619.
Whether Rundeck 3.0.23-20190619 is stable version?
From the https://bintray.com/rundeck/rundeck-rpm/rundeck able to see the Rundeck 3.0.23-20190619 is not yet published as GA.
2.11.14-1.70.GA is the latest GA version with build date 2019-09-13T03:37:04.000Z.
Will the application developed with 3.0.23-20190619 compatible with 2.11.14-1.70.GA?
Right now the latest stable release is 3.1.2, you can check the latest version in the changelog here. The "GA" notation is not used anymore. In some cases, you can see some updates of 2.11 / 3.0 branches focused on backports, not for new features, etc.
Your projects and jobs are compatible using 2.11, 3.0 and 3.1 branches.
This is not the first time it has happened, so I assume it's a bug where in the pipeline of NuGet Client / Visual Studio / NuGet server. A package has just been updated on NuGet.org. The latest version is 3.0.0.14. When I went to upgrade my package it couldn't find it and it said I had the latest version. After using Fiddler to see what was going over the wire, it's clear the NuGet Server is not serving the latest information. This call returns version 3.0.0.13 as the latest version.
https://api.nuget.org/v3/registration1/tweetmoasharp/index.json
Is that a bug on NuGet Server? Do they have a deliberate caching? Is it something the package publisher did that he didn't mark as a stable version?