sbp commented on issue #317:
URL:
https://github.com/apache/tooling-trusted-releases/issues/317#issuecomment-3538971767
The release manager ("count") experience is already split away because it's
on a different page. Compare #321 where in fact this split caused problems
because it was not obvious to @potiuk and I had to explain it. But it's
slightly complicated by the fact that to navigate to that page you must issue a
POST, because tallying is resource intensive, and the POST is currently issued
from the unified vote page. I think this is a reasonable compromise, but
alternative designs exist. We could, for example, continually poll for updates
to every vote thead currently open that ATR knows about. This would introduce
lag and be complex to implement, but it would mean that we could make the tally
a GET.
The only difference between the release manager and general non-release
manager contributor experiences is the existence of that button. We don't
record who the release managers are, so ever user gets that button, but it's
not a huge difference (just one button) and if a non-release manager clicks it,
it's fairly obvious that the resulting page is not for them. We're currently
allowing non-committee members to resolve votes, so we don't really have any
way of checking whether the tally page is or is not appropriate for a user.
--
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]
