You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tooling.apache.org by "sbp (via GitHub)" <gi...@apache.org> on 2026/02/23 14:51:16 UTC

[I] Make the user interface clearer in the finish phase (tooling-trusted-releases)

sbp opened a new issue, #753:
URL: https://github.com/apache/tooling-trusted-releases/issues/753

   This issue was reported by @hboutemy, and relates to PR #694. In a meeting, we agreed that the interface should be ordered like the current vote page so that the steps are obvious. We also agreed to rename various components on the page to make clear what they are and what they do without the user having to resort to documentation or explanation from a developer.
   


-- 
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: dev-unsubscribe@tooling.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Make the user interface clearer in the finish phase (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #753:
URL: https://github.com/apache/tooling-trusted-releases/issues/753#issuecomment-4209285094

   This will be a judgement call once we think finish is feature complete 


-- 
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: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Make the user interface clearer in the finish phase (tooling-trusted-releases)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp closed issue #753: Make the user interface clearer in the finish phase
URL: https://github.com/apache/tooling-trusted-releases/issues/753


-- 
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: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Make the user interface clearer in the finish phase (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
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: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Make the user interface clearer in the finish phase (tooling-trusted-releases)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #753:
URL: https://github.com/apache/tooling-trusted-releases/issues/753#issuecomment-3954641562

   When a release is announced, we freeze all the files in a directory in `state/finished/` in ATR. We also pseudo-publish these in a fake distribution area called "downloads" which is intended to simulate the eventual SVN directory and its downstream distribution websites. So we have `ATR finished` which is immutable, and we have `ATR downloads` (in alpha) or `SVN downloads` (in beta and onwards) which are mutable.
   
   All three of these areas only exist _post-announce_. Before a release manager uses the announce form, their files do not appear in any of those areas. Before announce, ATR has a directory called `state/unfinished/`.
   
   There are three phases in ATR: compose, vote, and finish. All of these use the `ATR unfinished` directory. You can create new revisions of your files in the compose and finish phases. Then you announce and the files go into `ATR finished`. They will also be linked into the `ATR downloads` (and eventually `SVN downloads`) areas.
   
   When testing with @hboutemy, the fact that we allow the creation of new revisions in the finish phase was confusing. In a meeting with @dave2wave today, he suggested off-hand that revisions could be fixed as soon as a vote starts. In other words, we could disallow release managers from creating revisions in the finish phase. This means that we would not have the file management interface to move files in that phase: we would remove that interface.
   
   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.
   
   From the ATR development side, we could have "revisions" of the downloads area. We would no longer need revisions in the finish phase. But we might not even need revisions of downloads either, because they would be tracked via SVN, so if we needed to revert then we could consult SVN history. It depends how efficient we need this to be.
   
   This might be more intuitive to release managers because the fact that ATR keeps a frozen copy of files is, as @hboutemy pointed out, an implementation detail.
   


-- 
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: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Make the user interface clearer in the finish phase (tooling-trusted-releases)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #753:
URL: https://github.com/apache/tooling-trusted-releases/issues/753#issuecomment-3946139320

   As part of this we also need to ensure that all paths are standardised.


-- 
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: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Make the user interface clearer in the finish phase (tooling-trusted-releases)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #753:
URL: https://github.com/apache/tooling-trusted-releases/issues/753#issuecomment-4297633615

   In ec2a4c1d82842cf4f803d87a95208776146df8a8 and 9a11abb5e95c54b09f330bcc2e4e525102e4de34, we moved the _form to move a file_ from the finish page to the compose page, partially resolving this issue, because now the ordering is not a consideration. Other requests from my notes were that we rename the distribution section to make it clear that these are third-party distributions, and that the announce email contain a link to the download folder by default.


-- 
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: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: [I] Make the user interface clearer in the finish phase (tooling-trusted-releases)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #753:
URL: https://github.com/apache/tooling-trusted-releases/issues/753#issuecomment-4299201180

   Resolved by 7fb6e56c604daa01bf963716bdbd36b501a1b35f, 857bbd54ed16755e83d0f524a41682c7ced5a375, and c8229307f7403a35cee5eb01550bea28d15973d8.


-- 
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: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org