What's wrong with keeping an entry called 'Upcoming changes' or '2.4 (unreleased)' up to date? It gives users an opportunity to review and provide feedback on upcoming changes since they're more visible. Then just switch the headline when you release, and you're good.
Putting the files in the repository has at least the problem that stable/bugfix branches (e.g. Subversion Plugin 2.4.x, Git Plugin 2.2.x, Maven Plugin 2.0.x), wouldn't work well with it AFAICT. Damien Nozay, contributor to Promoted Builds, may be interested in this as well, as he implemented something related for that plugin as well. Discussion (much of which does not apply here though): https://github.com/jenkinsci/promoted-builds-plugin/pull/54 On 15.12.2014, at 08:33, Bue Petersen <[email protected]> wrote: > Hi > > I have a suggestion or an idea.... > > I'm tired of the situation where I'm releasing a plugin, and then have to > update the plugin wiki page "just" after. There is always a bit of time-lack > where the new plugin release and the wiki isn't matching. > Quite often it is not a big problem, as the plugin wiki page isn't changed > much - but stil... > It would have been better to update it as we made decisions during > development and so on. > > How do you do it? > > I would like that we update the plugin wiki page during development (when > relevant), but first release it when the plugin is released. > Further I would much rather maintain the wiki page in markdown than in > Confluence. > > So my idea is to write the plugin wiki page in markdown (or maybe just > Confluence mark-up or what-ever), put this/these markdown files in the plugin > repository and upon release generate html/Confluence wiki mark-up and publish > it. > Confluence have an API for posting pages, but I think it requires some kind > of configuration on the server? > > Any thoughts on this? Are we the only one that would like this setup? I > couldn't find anything on this topic related to plugin development. > > Best regards, > Bue Petersen > > > > -- > 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/CAJB%2BB4VWDzFNszUiVzdrfi1hpe%3D4iC%2B3tvikizmSyv2ZNRFK4Q%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- 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/CB57535B-07AF-417F-AEAE-01A99B25C34D%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
