dave2wave commented on issue #753:
URL: 
https://github.com/apache/tooling-trusted-releases/issues/753#issuecomment-3954808393

   > But there's another alternative. We could consider that interface to be 
the planner for the ATR downloads or SVN downloads directory. We would freeze 
the release files as soon as the vote is started. When the vote succeeds, those 
files would still be frozen and ATR would retain them as a permanent record 
forever, internally. But the release manager should be able to rearrange and 
reorganise the downloads area as they see fit. From their point of view, they 
would be able to move and delete files (subject to certain constraints, such as 
not being able to change extensions; and perhaps we should be stricter than 
that). They would not be able to add files. But they would always be able to 
undo changes etc.
   
   This would really fit where we want to go with (1) switching the svn 
dist/release commits and (2) allowing for older releases to be archived. The 
new workflow in finish would be something like:
   
   1. Checkout the PMC's release directory at a shallow level.
   2. Moving the voted artifacts into that structure via the "planner"
   3. Optionally remove old artifacts from that structure via the "planner" - 
bonus for later is knowing the files from catalogued releases and easily 
removing them all with a single click.
   4. SVN Commit (the release will propagate to downloads.apache.org as now.) 
_**Important**_: make sure the svn log message identifies ATR, committee, 
project, and version including a note if archiving an old release.
   5. Do the upcoming catalog action.
   6. Distributions either make or check.
   7. Enable Announce button once the change is visible at downloads.apache.org 
and distribution check passes.


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to