sbp commented on issue #434: URL: https://github.com/apache/tooling-trusted-releases/issues/434#issuecomment-3703903971
That was the early plan, but we discussed it and decided that it would be better to remove the templating part from the vote and announce forms. So, before, you were shown two values: 1. EDITABLE. The template from the release policy. 2. NON-EDITABLE. The template with all values substituted. Now we show you this instead: 1. EDITABLE. The template with all values substituted. It's "2" from above, but it's editable. You can in fact still edit it in two different ways: either directly, in the textarea in the vote or announce form, or by modifying the original template, which you can still do by following a link we provide. Why do it this way? Because there are two layers of permanence here. One is that you have your template, your cookie cutter that you try to make _appropriate to all releases_. Otherwise it's not a very good template. The other is that you have the substituted, ready-to-go version which can be sent. You might want to customise this, but what customisations do you want to make? Do you want to make permanent customisations that should apply to all future messages too? Then edit the template. Or do you want to make customisations that only apply to this specific release? Then go ahead and edit the substituted version. This new design separates those two different modes of thinking. It doesn't really make sense to allow users to edit a template that is just about to be substituted if that template isn't being saved. That's what the old design asked you to do. One thing that might be useful is adding a details element containing some relevant information that might be useful, as values. It would be the equivalent of the list of template variable names. -- 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]
