Skip to content

Commit 56cb666

Browse files
authored
Update doc/source/how-to/deprecating.rst
1 parent bf46e41 commit 56cb666

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

doc/source/how-to/deprecating.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,13 @@ is used in this guide.
2424
the team at `[email protected] <pyansys_core_email_>`_. This step ensures that the
2525
deprecation is communicated effectively and that the team can assist with any necessary
2626
changes in the PyAnsys ecosystem.
27+
2728
2. **Close all open issues and pull requests**: Before deprecating the library, ensure that all
2829
open issues and pull requests in the library's repository are closed. This helps to avoid
2930
confusion and ensures that users are aware that the library is no longer actively maintained.
3031
You can close issues and pull requests with a comment explaining that the library is being
3132
deprecated and is no longer be supported.
33+
3234
3. **Create a deprecation issue**: Open an issue in the library's repository to announce the
3335
deprecation. This issue should explain why the library is being deprecated, what alternatives
3436
are available, and any relevant timelines. See a template below for the issue content.

0 commit comments

Comments
 (0)