It’s your call, but the Semantic Versioning Standard recommends 0.1.0: The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.
import java.io.*; public class ClassVersionChecker { public static void main(String[] args) throws IOException { for (int i = 0; i < args.length; i++) checkClassVersion(args[i]); } private static void checkClassVersion(String filename) throws IOException { DataInputStream in = new DataInputStream (new FileInputStream(filename)); int magic = in.readInt(); if(magic != 0xcafebabe) { System.out.println(filename + ” is not a valid … Read more
There are two ways to know the about Sybase version, 1) Using this System procedure to get the information about Sybase version > sp_version > go 2) Using this command to get Sybase version > select @@version > go
From the documentation you linked: ~1.2 is equivalent to >=1.2 <2.0.0, while ~1.2.3 is equivalent to >=1.2.3 <1.3.0 ^1.2.3 is equivalent to >=1.2.3 <2.0.0 The tilde depends on how many digits in the version number are given. The last digit given can vary. The caret is almost always the better choice because it acts similarly … Read more
I’ve recently heard a pithier versioning strategy, that I first encountered at Eric Elliot’s Medium account. It’s more weighted towards library versioning that customer facing version numbers, but it has the advantage of simplicity. Use a three part version number, where each number means: breaking.feature.fix breaking: Something has changed that means code/expectations must change feature: … Read more
[major].[minor].[release].[build] major: Really a marketing decision. Are you ready to call the version 1.0? Does the company consider this a major version for which customers might have to pay more, or is it an update of the current major version which may be free? Less of an R&D decision and more a product decision. minor: … Read more