This is an automated email from the ASF dual-hosted git repository.
sebb pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/attic.git
The following commit(s) were added to refs/heads/main by this push:
new 94c72f2 retire.py not yet available
94c72f2 is described below
commit 94c72f2f0e76724f1bb49971f48c6a8cd8a2e0c9
Author: Sebb <sebb...@users.noreply.github.com>
AuthorDate: Thu May 1 09:23:22 2025 +0100
retire.py not yet available
---
process.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/process.md b/process.md
index 1447aca..76e369a 100644
--- a/process.md
+++ b/process.md
@@ -40,9 +40,8 @@ to move that PMC into the Attic and gently close it down.
that is grounds for moving to the Attic. They should inform the board as
above, noting that the vote
failed to get enough votes.
1. If the board approves the resolution, open an [Attic
JIRA](https://issues.apache.org/jira/browse/ATTIC)
- item - 'Move ${project} to the Attic'. The Attic PMC will step in and
create a detailed issue
- description using
[`retire.py`](https://github.com/apache/attic/blob/main/retire.py),
- with other generated parts to move the project to the Attic.
+ item - 'Move ${project} to the Attic'.
+ **TBA: this was previously generated by retire.py, but it has yet to be
converted to the new formats.**
Generated issue content typically contains following steps (see ["How
to"](#how-to-general-pointers) below for a description
of each step):
- [#](#how-to-1-confirm-board-resolution) Confirm Board Resolution
