Versions Compared

Key

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

...

Component

Proposed Version

Version in <Last SIMP Release>

Latest Version

Unit Test Status

Acceptance Test Status

GitHub Released

Forge Released

RPM Released

Changelog

component-name

1.2.3

1.2.2

1.3.0

PASSED

<Link to Travis CI>

PASSED

<Link to GitLab CI>

Y

(or N)

N

(Could be Y or N/A)

Y

(or N)

<links if appropriate>



















...


ID

Ticket Summary (< 100 chars)

Test Description

Component

Blocker Ticket

Story Points

Alpha (Y/N)

RC1 (Y/N)

Final (Y/N)

El6 (Y/N)

EL7 (Y/N)

EL8 (Y/N)

OEL6 (Y/N)

OEL7 (Y/N)

OEL8 (Y/N)

RH6 (Y/N)

RH7 (Y/N)

RH8 (Y/N)

Status

Notes

1

Release Components

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

3

Y

Y

Y

N

N

N

N

N

N

N

N

N

1-1

Identify components to release

1

1-2

Release components

2

2

Update simp-core pre-release tests

Update simp-core default, ipa, and install_from_tar acceptance test suites for release-impacting changes. This includes updating the nodesets for the supported OSs.

simp-core

5

Y

N

N

N

N

N

N

N

N

N

N

N

Tests will be executed for the appropriate OSs permutations in the nodeset, but separate tickets per OS should not be created.

2-1

Update tests

4

2-2

Review updates

1

53

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 default acceptance test suite passes. Pushing to GitLab will execute the

simp-core

1

3



3-1

Update files and test

2

3-2

Review updates

1

2

Verify installation from RPM








3

Create and verify Changelog.rst


simp-core




This addresses STIG updates and Compliance Markup modules changes.

4

'Upgrading SIMP' has an entry for the latest version and is correct


simp-doc





5

SIMP server upgrade from RPM using the upgrade instructions.  Document any steps that are needed outside the ordinary upgrade.  Then, if there are additional steps, have someone else use the docs to do the upgrade to verify.







Manual tests for now. Will migrate to simp-integration_test for automated upgrade test.

this should be done for servers in both FIPS and NOFIPS mode.

7

RPMs have been uploaded to packagecloud







in simp-core run

  • SIMP_BEAKER_OS=oel beaker:suites[install_from_rpm]

  • beaker:suites[install_from_rpm]

  • beaker:suites[install_from_rpm,el6_server]

  • SIMP_BEAKER_OS=oel beaker:suites[install_from_rpm,el6_server]

and then do it all again with BEAKER_fips=yes

...