-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Welcome to the Vigilante wiki!
Vigilante is an inventory and issue tracking system for security teams. This app was originally written for Pine Fur Con in South Portland, Maine, but it is designed to be used by any security team.
Current status: Pre-Alpha
We will begin pushing builds once we reach the beta phase. These beta builds will be versioned by build number in the following format: Vigilante-Beta-####
. Support for beta builds will be provided via GitHub issues.
Once we reach the Release stage, we will begin releasing LTS and Edge builds. LTS builds will be provided using the following format: Vigilante-LTS-X.Y.Z
. Edge builds will be provided using the following format: Vigilante-Edge-X.Y.Z
.
-
X
- Major release number. This will begin with 1. It will be rare for this number to be incremented. -
Y
- Minor release number. This will begin with 0. It will be incremented every time a major stable feature is added. -
Z
- Patch release number. This will begin with 0. It will be incremented for every stable service pack release.
Service packs will be comprised of a number of changes from bug fixes, security patches, or small features or UI updates.
LTS builds are provided for Long Term Support. This is the recommended stable version for running in Enterprise applications. Updates to LTS builds will only be provided in the event of security issues or bugs which may cause data destruction or loss of ability to use the service. Edge builds are provided for users who want extra features or bug fixes, but don't mind a more frequent update cycle. These edge builds should be considered stable, however they are not recommended for Enterprise use.
If an LTS build is version 1.5.x
, the Edge build will be 1.6.x
. The patch number is insignificant here. Instead, it should be considered that the 1.5 branch is LTS and 1.6 is Edge. In this example, any versions before 1.5 are unsupported.
These instructions will come when we feel Vigilante is ready for production use.
For those wishing to contribute to the project, there are four projects you can contribute to:
- Core
- Database
- Services
- Web
For (most) contributions, you should also contribute to the Tests project and add the appropriate unit tests for the change you made.