sbp commented on issue #363: URL: https://github.com/apache/tooling-trusted-releases/issues/363#issuecomment-3702415599
@developer-ravi-03 Thank you. This is more complicated than it appears (and more complicated than #449) because it depends how we resolve #434, and we need to choose a syntax. I'm still surprised that the current design is so unintuitive, and I'm starting to think that we should just show the substituted version in the actual vote form, but remind the user that they can always edit the template in the release policy interface. Also I found a bug: the release checklist needs to be substituted before it gets substituted into an email body. I've filed this as #451. Therefore I think the correct resolution to this issue is actually to allow email subjects to be templated, but to add this as a release policy field just before the current vote email subject field. The same must go for announcements emails too, so a release policy field needs to be added for that. The user should be told in a description, most likely, that the email can be edited "for this and future releases" by using the field in the release policy, with an appropriate link to the release policy field. That will no doubt require `Widget.CUSTOM` to be used. When we created this issue we thought it was a "good first issue" (or second issue in this case!) because we figured we would be using a similar interface to the current field, but I think perhaps it is a little more advanced than that now. What do you think? -- 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]
