MilanVavra / SQLite3

The mcz files in this repository are using Monticello branches. This way
multiple versions of the project can be kept in one repository and be
easily distinguished from one another.

Monticello package version numbers are branch local. Meaning each branch
starts its numbering from one.

For example in the Monticello package name
SQLite3.mva-squeak5.0-rel1.0-2017_02_12.1.mcz
the package name is
SQLite3
the branch is
mva-squeak5.0-rel1.0
the author identification is
2017_02_12
and version number is
1

A branch is determined from the Monticello package name like this:
1) strip the shortest suffix starting with dash
2) from the result of 1) strip the shortest prefix ending with dot

Let's take
SQLite3.mva-squeak5.0-rel1.0-2017_02_12.1.mcz
as an example.
Here 1) yields
SQLite3.mva-squeak5.0-rel1.0
stripping the suffix
-2017_02_12.1.mcz
And 2) yields
mva-squeak5.0-rel1.0
stripping the prefix
SQLite3.


Instead of author identification in the name, a date of the commit is
used in the form YYYY_MM_DD. This way the name contains the date of the
last commit - the version number of which follows it. This makes the
filenames sort in the order of the branches and commit dates on the
branches.

The author is still recorded inside the archive. Just not in the filename.

Ordering in Repository browser by author can show you the timeline of the
commits across branches.

The branch naming convention used here is
1) branch author identification
2) target identification with version number
3) development or release version with version number

Let's take
SQLite3.mva-squeak5.0-rel1.0-2017_02_12.1.mcz
as an example.
The branch name here is
mva-squeak5.0-rel1.0
as explained above.
We get
mva
as branch author identification
squeak5.0
as target identification with version number
rel1.0
as release version with version number
.