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.
Related
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 installed material-ui/lab: 4.0.0-alpha.60,
in my project, which is an alpha version that the Material-UI team doesn't recommend using in production projects.
I checked the versions here, but I didn't find anything other than the alpha version.
What is the official release of #material-ui/lab, or what alternative I can use instead of it?
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.
I'm using NuGet to manage libraries used in my solution. But I wonder how often the libraries inside NuGet gets updated. For example, on 10 April 2019, jQuery 3.4.0 has been released, but as of today, the latest jQuery package on NuGet is more than 1 year old.
3.3.1 2,970,912 1/22/2018
I need to manually download the jQuery library from their website in order to use the latest version, but this beats the advantage of using NuGet. So my question is that how often is this updated? Is someone from Microsoft needs to add the library manually every time? Or does the library developer has to push the updates to NuGet (and I wonder why they have not done so if this is the case - now is more than 2 weeks after release date)?
I want to create an MSI installer containing three apps. I will be releasing frequent updates to each app as I work through the list of feature requests and do bug fixes. The three apps are currently at versions 1.6.3, 1.6.12 and 1.8.1 respectively.
I was wondering what you guys can recommend for the version of the package. Should I:
Make the package version independent of the versions of the individual apps ?
Change the apps so they always have the same version as each other ?
Some other suggestion ?
Modify the package version each time the version of one of the apps changes. Then, you can look at the package version and know exactly which version of each app was being used.
Example:
Main version 1.4.1 has (1.6.3, 1.6.12, 1.8.1)
Main version 1.4.2 has (1.6.3, 1.6.13, 1.8.1)
Main version 1.5.0 has (1.7.0, 1.6.13, 1.8.2)
Main version 2.0.0 has (1.7.0, 1.6.14, 2.0.0)
So, if you're doing a minor version upgrade to one of your apps, the main application also goes up by a minor version number. Major changes to a sub-app result in the main app also getting a major version number change.