Skip to content

Commit

Permalink
DOC: Update release instructions
Browse files Browse the repository at this point in the history
  • Loading branch information
pllim committed Dec 21, 2023
1 parent e8f125e commit db42b0c
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/dev/release.rst
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Package Release Instructions

This document outlines the steps for releasing a versioned Jdaviz package to
PyPI. Currently, these do not cover submitting package updates to other
distribution outlets, such as ``astroconda`` or ``conda-forge``.
distribution outlets, such as ``conda-forge``.

This process currently requires you (the release manager) to have sufficient GitHub
permissions to tag, push, and create a GitHub release on Jdaviz repository. These
Expand Down Expand Up @@ -89,8 +89,8 @@ You can do a release from your fork directly without a clean code check-out.
git commit -m "Preparing release vX.Y.0"
#. Push the ``vX.Y.x`` branch to upstream.
Make sure the CI passes. If any of the CI fails, especially the job that
says "Release", abandon this way. Stop here; do not continue! Otherwise,
Make sure the CI passes. If any of the CI fails,
abandon this way. Stop here; do not continue! Otherwise,
go to the next step.

#. Go to `Releases on GitHub <https://github.com/spacetelescope/jdaviz/releases>`_
Expand Down Expand Up @@ -295,8 +295,8 @@ instances of ``vX.Y.x`` with ``v3.5.x``.
git commit -m "Preparing release vX.Y.Z"
#. Push the ``vX.Y.x`` branch to upstream.
Make sure the CI passes. If any of the CI fails, especially the job that
says "Release", abandon this way. Stop here; do not continue! Otherwise,
Make sure the CI passes. If any of the CI fails,
abandon this way. Stop here; do not continue! Otherwise,
go to the next step.

#. Go to `Releases on GitHub <https://github.com/spacetelescope/jdaviz/releases>`_
Expand Down

0 comments on commit db42b0c

Please sign in to comment.