I have argued for getting rid of the “feature” of sucking in
`{excerpt}`s from the wiki for display in the update center (it is an
infrastructure headache), and I would likewise argue that a revamped
plugin list should obtain all of its metadata from the same source the
update center does, which should be plugin `*.hpi` files exclusively.
In other words, it does not matter where you host the plugin or how
you build it, so long as you conform to a documented file format and
publish to the specified artifact repository.Now metadata could include _links_ to additional information (user guides, etc.) which could live anywhere. Changelogs demand special consideration, though: it is long-form content which really needs to be in a machine-readable format so it can be displayed in different modes. For example, if you are looking at the _Updates_ screen inside Jenkins, you could click an expand button next to a plugin and see a list of changes since the installed version. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0UQnCK-E_9aLiM46sQ6xeP0KBYYjNSjVMu8X-ecRH9xw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
