dave2wave commented on issue #1560:
URL:
https://github.com/apache/tooling-trusted-releases/issues/1560#issuecomment-5516699199
1. Create ATR Committee
Use automation to either watch projects.a.o and whimsy.a.o versions of
committee-info and podlings.xml, or read these directly with svn pubsub.
2. Move/rename ATR Committee
This is either a rename, or a move and rename. The podlings.xml file has
an attribute to indicate the change. There are exceptions where a PMC is formed
while renaming a podling.
3. Archive ATR Committee
This can be detected when all of a PMC's or podling's svn dist dev and
release areas are removed via `svn rm`. It can also be detected by the ldap
group being deleted.
4. Create Project
This can be done as part of Create ATR Committee
5. Move/rename Projects
By itself this is for moving projects to the attic. It is detected when
all of a PMC's svn dist dev and release areas are removed via `svn rm`.
6. Move/rename Projects + Releases
It is detected when all of a PMC's or Podling's svn dist dev and release
areas are moved via `svn mv`.
7. Archive Project and Releases
It is detected when all of a PMC's or Podling's svn dist dev and release
areas are moved via `svn mv`.
8. Delete Release Candidates
This is always done when you "archive atr committee"
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
