From this section, it is obvious that we need to follow this rule:
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes.
- MINOR version when you add functionality in a backward compatible manner.
- PATCH version when you make backward compatible bug fixes.
If we need to put pre-release label and/or build metadata, we can extend the semver into MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD] format.
In order to support centralized golang library, we will implement all packages inside a single repository. Each package is independent, so it will have its own go.mod file and its own version. Here are some important notes
github.com/username/repository/pkg/path with pkg/path/v1.X.Y tag.github.com/username/repository/pkg/path/v2 with pkg/path/v2.Y.Z tag./vX directory if we are not supporting old version.Personally I'm kinda forget why or when this problem occured, but this was written inside my sacred black note. So I'll put it here in case this will be a recurring problem.
Basically, if EXT4 partitions are broken by accident and they need to be repaired, we will use fsck command to fix it.
sudo fsck.ext4 -y /dev/sda[number]
Source: https://askubuntu.com/questions/910078/structure-needs-cleaning-error-cannot-mount-partition
Recently I was researching about infrastructure providers for my personal system. When I was comparing at their products, it is confusing which one is the most suitable and cost-efficient for my services. Well, this is my personal notes and somehow this image appeared among the search results
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.