latest
  • Welcome to the SIMP documentation!
  • 1. Quick Start
  • 2. Changelogs
  • 3. Getting Started
  • 4. User Guide
  • 5. Contributing to SIMP
    • 5.1. Introduction
    • 5.2. Contribution Procedure
    • 5.3. Maintenance Procedure
      • 5.3.1. Amending Changes to Submitted Pull Requests
      • 5.3.2. Tagging and Releasing Components
        • 5.3.2.1. Component Versioning
        • 5.3.2.2. SIMP-Owned Puppet Module Tag And Release Procedures
        • 5.3.2.3. Other Puppet Module Release Procedures
        • 5.3.2.4. Ruby Gem Release Procedures
        • 5.3.2.5. Other ISO-Related Project Release Procedures
        • 5.3.2.6. ISO Release Procedures
    • 5.4. Testing on FIPS Systems
    • 5.5. Useful Resources
  • 6. Security Concept of Operations
  • 7. Security Control Mapping
  • 8. Vulnerability Supplement
  • 9. Help
  • 10. License
  • 11. Contact
  • 12. Glossary of Terms
 
SIMP
  • Docs »
  • 5. Contributing to SIMP »
  • 5.3. Maintenance Procedure »
  • 5.3.2. Tagging and Releasing Components »
  • 5.3.2.5. Other ISO-Related Project Release Procedures
  • Edit on GitHub

5.3.2.5. Other ISO-Related Project Release ProceduresΒΆ

This section will describe the release procedures we use for the miscellaneous, non-Puppet-module components required to build a SIMP ISO. The relevant components include

  • rubygem-simp-cli
  • simp-adapter
  • simp-doc
  • simp-environment
  • simp-gpgkeys
  • simp-rsync
  • simp-utils

For demonstration purposes, we will be using the simp-adapter project, which uses the master branch as its development branch.

  • 5.3.2.5.1. Pre-Release Checklist
  • 5.3.2.5.2. Release to GitHub
  • 5.3.2.5.3. Build Signed RPM and Deploy to Download Server
Next Previous

© Copyright 2020, THE SIMP TEAM. Revision 30a60b40.

Built with Sphinx using a theme provided by Read the Docs.