Versions Compared

Version Old Version 66 New Version 67
Changes made by

Liz Nemsick

Liz Nemsick

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ID

Ticket Summary (< 100 chars)

Description

Component

Blockers

Story Points

EL7

EL8

OEL7

OEL8

RH7

RH8

Notes

1

Release Components

Identify components to be released, verify tests pass, push annotated tags, update SIMP release confluence page. https://simp.readthedocs.io/en/latest/contributors_guide/maintenance/Tagging_and_Releasing_Components.html

NOTE: This excludes simp-doc, which is addressed a separate ticket after all documentation updates have been completed.

-

3

-

-

-

-

-

-

1.1

Identify components to release

-

1

-

-

-

-

-

-

1.2

Release components

1.1

2

-

-

-

-

-

-

2

Update simp-core with released components

Update simp-core files (Puppetfile.pinned, metadata.json, src/assets/simp/build/simp.spec) and verify ISOs can be built and the default, ipa, and simp_lite acceptance test suites pass.

You must set the SIMP_FULL_MATRIX variable to have all the tests run in a GitLab.

All components in the Puppetfile.pinned except simp-doc should be referencing a GitHub tag. simp-doc is addressed in another ticket.

simp-core

1

3

-

-

-

-

-

-

2.1

Update files and build ISOs for supported OSs

You may need to update package lists for the ISO builds.

 

-

2

-

-

-

-

-

-

 

2.2

Verify acceptance tests

Verify the default, ipa, and simp_lite acceptance tests pass with new components. No major test revisions should be needed.

 

2.1

1

-

-

-

-

-

-

2.3

Review updates

 

 

2.2

1

-

-

-

-

-

-

18

Verify simp/simp_core meta module

Verify that the simp/simp_core meta module has appropriate dependencies and its dependencies have all been published to PuppetForge by running the install_from_core_module test suite.

4

-

-

-

-

-

-

18.1

Execute check for PuppetForge publication

Execute ‘bundle exec rake puppetfile:check’ and examine output to identify any modules that have not been published to PuppetForge

-

-

-

-

-

-

18.2

Publish any missing modules to PuppetForge

-

-

-

-

-

-

18.3

Update the install_from_core_module test with any release-specific changes

-

-

-

-

-

-

18.4

Execute the install_from_core_module test

-

-

-

-

-

-

17

Dogfood released modules and assets

Use released modules in development environments that exercise as many of the modules as possible. Install RPMs of released assets on SIMP servers.

5

Y

Y

-

-

-

-

17.1

Deploy modules to development environments

Update Puppetfiles for development environments and deploy the modules.

-

-

-

-

-

-

17.2

Install asset RPMs on SIMP server

Install RPMs and watch for any RPM installation error messages.

-

-

-

-

-

-

17.3

Examine logs for issues

-

-

-

-

-

-

3

Update Changelog for bug fixes

simp-doc

2

3

-

-

-

-

-

-

3.1

Identify bug fixes and update changelog

-

2

-

-

-

-

-

-

3.2

Review changes

3.1

1

-

-

-

-

-

-

4

Review ‘Quick Start’ Guide

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

4.1

Review and update

-

-

-

-

-

-

4.2

Review changes

4.2

-

-

-

-

-

-

5

Review ‘Getting Started’ Guide

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

5.1

Review and update

-

-

-

-

-

-

5.2

Review changes

5.2

-

-

-

-

-

-

6

Review ‘User Guide’

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

6.1

Review and update

-

-

-

-

-

-

6.2

Review changes

6.2

-

-

-

-

-

-

7

Review ‘HOWTO’

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

7.1

Review and update

-

-

-

-

-

-

7.2

Review changes

7.2

-

-

-

-

-

-

8

Review ‘FAQ’

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

8.1

Review and update

-

-

-

-

-

-

8.2

Review changes

8.2

-

-

-

-

-

-

9

Review ‘Help’ and ‘Contact’ sections

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

9.1

Review and update

-

-

-

-

-

-

9.2

Review changes

9.2

-

-

-

-

-

-

10

Review ‘Glossary of Terms’

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

10.1

Review and update

-

-

-

-

-

-

10.2

Review changes

10.2

-

-

-

-

-

-

2211

Review security documentationGeneral review of security-related documentation‘Security Concept of Operations’

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

This is required for each major release, nice-to-have for each minor release, and not necessary for each patch release.

Subtasks should correspond to major sections of the documentation, an will need to be updated accordingly when the docs structure changes.

11

Review ‘Security Concept of Operations’

11.1

Review and update

-

-

-

-

-

-

11.2

Review changes

11.2

-

-

-

-

-

-

12

Review ‘Security Control Mapping’

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

12

Review ‘Security Control Mapping’

.1

Review and update

-

-

-

-

-

-

12.2

Review changes

12.2

-

-

-

-

-

-

13

Review ‘Vulnerability Supplement’

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.

simp-doc

-

-

-

-

-

-

13

Review ‘Vulnerability Supplement’

.1

Review and update as necessary. This is a general review to make sure the information is accurate and intelligible.simp-doc

-

-

-

-

-

-

13.2

Review changes

13.2

-

-

-

-

-

-

2314

Finalize simp-doc

2314.1

Remove any reference to release candidates

2314.2

Release4

14.2

15

Update simp-core with released simp-doc and verify versions

Update simp-core Puppetfile.pinned

All components in the Puppetfile.pinned should be referencing a GitHub tag.

simp-core

1

3

-

-

-

-

-

-

415.1

Update files and build ISOs

-

2

-

-

-

-

-

-

415.2

Verify versions

Make sure there are no version discrepancies in the Puppetfile.pinned, metadata.json and simp.spec files.

415.1

1

-

-

-

-

-

-

18

Verify simp/simp_core meta module

Verify that the simp/simp_core meta module has appropriate dependencies and its dependencies have all been published to PuppetForge by running the install_from_core_module test suite.

4

-

-

-

-

-

-

18.1

Execute check for PuppetForge publication

Execute ‘bundle exec rake puppetfile:check’ and examine output to identify any modules that have not been published to PuppetForge

-

-

-

-

-

-

18.2

Publish any missing modules to PuppetForge

-

-

-

-

-

-

18.3

Update the install_from_core_module test with any release-specific changes

-

-

-

-

-

-

18.4

Execute the install_from_core_module test

-

-

-

-

-

-

17

Dogfood released modules and assets

Use released modules in development environments that exercise as many of the modules as possible. Install RPMs of released assets on SIMP servers.

5

Y

Y

-

-

-

-

17.1

Deploy modules to development environments

Update Puppetfiles for development environments and deploy the modules.

-

-

-

-

-

-

17.2

Install asset RPMs on SIMP server

Install RPMs and watch for any RPM installation error messages.

-

-

-

-

-

-

17.3

Examine logs for issues

-

-

-

-

-

-

5

Create final ISO, verify with simp-packer, and publish the ISOs and their tar files

This is the final build and spot check via simp-packer.

simp-core

4

Y

Y

-

-

-

-

5.1

Build ISO

Use official RPM signing keys when the artifacts are to be published anywhere at simp-project.com.

-

1

-

-

-

-

-

-

5.2

Build BIOS boot box with FIPS enabled and encrypted disk

5.1

-

-

-

-

-

-

5.3

Build BIOS boot box with FIPS enabled and unencrypted disk

5.1

-

-

-

-

-

-

5.4

Build BIOS boot box with FIPS disabled and encrypted disk

5.1

-

-

-

-

-

-

5.5

Build BIOS boot box with FIPS disabled and unencrypted disk

5.1

-

-

-

-

-

-

5.6

Build UEFI boot box with FIPS enabled and encrypted disk

5.1

-

-

-

-

-

-

5.7

Build UEFI boot box with FIPS enabled and unencrypted disk

5.1

-

-

-

-

-

-

5.8

Build UEFI boot box with FIPS disabled and encrypted disk

5.1

-

-

-

-

-

-

5.9

Build UEFI boot box with FIPS disabled and unencrypted disk

5.1

-

-

-

-

-

-

5.10

Publish artifacts

Final artifacts that have passed simp-packer validation are published to official release folders at simp-project.com.

5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9

1

-

-

-

-

-

-

19

Announce release

5

-

-

-

-

-

-

20

Post-release: Verify RPM publication

Verify RPMs have been uploaded to simp-project.com. This includes Puppet module RPMs, SIMP application RPMs, and any other auxiliary, application RPMs.

20.1

Verify Puppet module RPMs have been published

Execute ‘bundle exec rake puppetfile:check’ and examine output to identify any modules that have not been published to simp-project.com.

20.2

Verify other RPMs have been published

Run the install_from_rpm test. See https://github.com/simp/simp-core/blob/master/spec/acceptance/suites/README.md . If a nodeset for the OS under test does not exist, create it.


Y

Y

20.3

Publish any missing RPMs

...