recentpopularlog in


« earlier   
AWS Lambda — how best to manage shared code and shared infrastructure
In the last post I discussed the pros & cons of following the Single Responsibility Principle (SRP) when moving to the serverless paradigm. One of the questions that popped up on both Twitter and…
aws  lambda  srp  single  responsability  shared  code  deployment  versioning  backward  compatibility  isolation  failure 
19 hours ago by vonc
Chris's Wiki :: blog/programming/FallibleSemverAndMVS
In package management and versioning, the problem of version selection is the problem of what version of package dependencies you'll use. If your package depends on another package A, and you say your minimum version of A is 1.1.0, and package A is available in 1.0.0, 1.1.0, 1.1.5, 1.2.0, and 2.0.0, version selection is picking one of those versions. Most package systems will pick the highest version available within some set of semantic versioning constraints; generally this means either 1.1.5 or 1.2.0 (but not 2.0.0, because the major version change is assumed to mean API incompatibilities exist). In MVS, you short-circuit all of this by picking the minimum version allowed; here, you would pick 1.1.0.
versioning  devops 
yesterday by euler
.NET Core versioning | Microsoft Docs
.NET Core is made of NuGet packages, tools, and frameworks that are distributed as a unit. Each of these platform layers can be versioned separately, enabling better agility. While there is significant versioning flexibility in that regard, there's also a desire to version the platform as a unit to make the product easier to understand.

This article aims at clarifying how the .NET Core SDK and runtime are versioned.

There are lots of moving parts that version independently in .NET Core. However, starting with .NET Core 2.0, there is an easy to understand top-level version number that everybody understands to be the version of ".NET Core" as a whole. The rest of this document goes into the details of the versioning of all those parts. These details can be important if you're a package manager, for example.
dotnet  core  versioning  converntions  version  NuGet 
7 days ago by coffeebucket
Fossil is a simple, high-reliability, distributed software configuration management system with these advanced features
development  software  tools  versioning 
13 days ago by mark.larios

Copy this bookmark:

to read