<commit_before># Chef Push Jobs Server Release Process

## Document Purpose

The purpose of this document is to describe the *current* release
process such that any member of the team can do a release.  As we
improve the automation around the release process, the document should
be updated such that it always has the exact steps required to release
Chef Push Jobs Server.

This document is NOT aspirational.  We have a number of automation
tools that we intend to use to improve the release release process;
however, many are not fully integrated with our process yet. Do not
add them to this document until they are ready to be part of the
release process and can be used by any team member to perform a
release.

## Pre-requisites

In order to release, you will need the following accounts/permissions:

- Local checkouts of the opsocde-pushy-server and chef-web-downloads repositories
- Push access to the opscode-pushy-server github repository
- Chef Software, Inc Slack account
- VPN account for Chef Software, Inc.
- Account on [https://discourse.chef.io](https://discourse.chef.io) using your Chef email address
- Login for wilson.ci.chef.co (This is linked to your github account.)
- Access to artifactory.chef.co
- Access to delivery.chef.co

## THE PROCESS
### Informing everyone of a pending release.

- [ ] Announce your intention to drive the release to #cft-announce on slack.
- [ ] Cross-post this intention on #chef-server and #pool.  Determine whether
  this upgrade requires a major/minor/patch bump and what the major changes
  are.
- [ ] Ensure that the opscode-push-jobs-server pipeline on wilson is currently green - you
  cannot ship if master is broken.

### Preparing for the release

- [ ] Update CHANGELOG.md to contain all of the changes needed in this release.
- [ ] Check RELEASE_NOTES.md to ensure that it describes the
  most important user-facing changes in the release. This file should
  form the basis of the post to Discourse that comes in a later step. Update as
  appropriate.  If a there is a major version change, transfer all
  contents to PRIOR_RELEASE_NOTES.md before adding release notes.
- [ ] Open a PR with these changes and post the link to #chef-server-rfr<commit_msg>RELEASE_PROCESS: remove item never done<commit_after># Chef Push Jobs Server Release Process

## Document Purpose

The purpose of this document is to describe the *current* release
process such that any member of the team can do a release.  As we
improve the automation around the release process, the document should
be updated such that it always has the exact steps required to release
Chef Push Jobs Server.

This document is NOT aspirational.  We have a number of automation
tools that we intend to use to improve the release release process;
however, many are not fully integrated with our process yet. Do not
add them to this document until they are ready to be part of the
release process and can be used by any team member to perform a
release.

## Pre-requisites

In order to release, you will need the following accounts/permissions:

- Local checkouts of the opsocde-pushy-server and chef-web-downloads repositories
- Push access to the opscode-pushy-server github repository
- Chef Software, Inc Slack account
- VPN account for Chef Software, Inc.
- Account on [https://discourse.chef.io](https://discourse.chef.io) using your Chef email address
- Login for wilson.ci.chef.co (This is linked to your github account.)
- Access to artifactory.chef.co
- Access to delivery.chef.co

## THE PROCESS
### Informing everyone of a pending release.

- [ ] Announce your intention to drive the release to #cft-announce on slack.
- [ ] Cross-post this intention on #chef-server and #pool.  Determine whether
  this upgrade requires a major/minor/patch bump and what the major changes
  are.
- [ ] Ensure that the opscode-push-jobs-server pipeline on wilson is currently green - you
  cannot ship if master is broken.

### Preparing for the release

- [ ] Update CHANGELOG.md to contain all of the changes needed in this release.
- [ ] Check RELEASE_NOTES.md to ensure that it describes the
  most important user-facing changes in the release. This file should
  form the basis of the post to Discourse that comes in a later step. Update as
  appropriate.
- [ ] Open a PR with these changes and post the link to #chef-server-rfr
{'fraction_non_alphanumeric': 0.05427782888684453, 'fraction_numerical': 0.0, 'mean_word_length': 3.925254813137033, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7013074', 'n_tokens_mistral': 1188, 'n_tokens_neox': 1129, 'n_words': 632}