Hi Animesh,
The following lines are my idea.
The version number could be in a popular format
major.minor.patch
1. The master branch keeps the major & minor SNAPSHOT versions. (e.g.
1.0.0-SNAPSHOT, 1.1.0-SNAPSHOT, 2.0.0-SNAPSHOT)
2. The release branch (e.g. branch-1.0) keeps the patched
Hi Dawn,
what specifically do you have in mind? I agree that once we start to have
periodic releases (hopefully soon) we will tag corresponding git branch
with the version number. Since, there is no release, all the code is in the
master branch.
If you tell us what do you have in mind, we can
Hi all,
I am not in the Crail team and I have a suggestion. Perhaps the Crail
project could use Spark's branching model? I think it is very simple and
practical
