FOGProject starting point
Introduction
FOG is a free open-source cloning/imaging/rescue suite/inventory management system. FOG can be used to image Windows XP, Vista, Windows 7, Windows 8/8.1, Windows 10, and Windows 11 PCs using PXE, PartClone, and a Web GUI to tie it together. Includes features like memory and disk test, disk wipe, av scan, task scheduling, inventory management, remote deployment of OS's, and remote installation of software packages. Features can be triggered through the web GUI, once the client machine has been registered with FOG.
Versioning and branches
FOG uses a versioning schema that follows the general principles of semantic versioning with some adjustments to fit the development lifecycle. You can find the automatic release workflows in the fog-workflows repo and the distro install tests in https://github.com/FOGProject/fogproject-install-validation
| Workflow | Status |
|---|
| Release | |
| RHEL Distros | |
- The default branch of
stable will always have the latest patch release, for most users this is where you want to install from.
- The
master branch has the baseline of the latest Minor release. You should not typically install from here as it won't include security patches released since the baseline was set.
dev-branch is where the latest patch release changes are staged and tested. You can install from dev-branch to help test bug-fixes, security-fixes, and minor feature enhancements on a more frequent cadence.working-* and feature-named branches are where work on the next Major or Minor release take place. They can be used to install and test the current beta version or specific working features.
This gives us a Production, Staging, and Dev branches to follow standard devops practices.
| Dev Cycle Stage | Channel | Branches | Version Property Associated |
|---|
| Production | stable | stable, master | Minor and Patch |
| Staging | patches | dev-branch | Patch |
| Dev | beta | working-*, {feature-name} | Major, Minor |
The Channel column is the value to put in FOG_update_channel in
.fogsettings, or to pass to bin/updatefog.sh --channel. It is the same word
as the FOG_CHANNEL your server reports, in lowercase — one vocabulary for
both, so the value you configure and the value you read back agree.
The earlier spellings staging and dev mean patches and beta
respectively, and are still accepted so existing servers keep updating. They
are no longer the documented names: dev in particular pointed at
working-1.6, not at dev-branch, which read as a typo and was not one.
See also: Version Sync Automation for how FOG_VERSION/FOG_CHANNEL are kept in sync with git state on each branch.
Current version on each of the main branches (updated automatically - see the doc above):
This is the beginning of the README. Read the rest at the original. Read the full README ↗
