Skip to content

Latest commit

 

History

History
29 lines (21 loc) · 1.47 KB

BUILD.md

File metadata and controls

29 lines (21 loc) · 1.47 KB
Raw

Build

Just run build.cmd. In folder build you now see two subfolders:

  • bin: compiled output files
  • dist: packages for distribution

Prepare new release

This projects follows GitFlow. The master branch contains the latest released version. Each released version is tagged with a version tag: this tag follows Semantic Versioning. Ongoing development takes place in develop branch. When preparing for a new release the last steps before merging develop to master is to change the version informations (e.g. 0.1.0-alpha):

  • KeeAnywhere\Properties\AssemblyInfo.cs
  • build.cmd
  • version_manifest.txt (change only for production releases)

After merging develop to master change version in develop to next unstable version (e. g. 0.2.0-unstable) - just to make clear ths is a development snapshot and generally not released to public.

Version examples

Versions are always counted upwards. Each version is unique. Additional informations like alpha, beta only describe the characteristics of the version. Until version 1.0.0 the minor version will be increased.

  • 0.1.0-alpha: Alpha release for previewing or testing new features. Not for production use.
  • 0.2.0-unstable: Current development snapshot. These versions will never be released to public.
  • 0.2.0-beta: Beta releases are feature complete. Only bugfixing should take place before a new main release
  • 1.0.0: production version