Hi Daniel and Daniel
Thanks for the feedback, refs and thoughts - I very much appreciated it. So
I just want to post my feed back here (possible for others to read as
well)...
Daniel Beck wrote:
What's wrong with keeping an entry called 'Upcoming changes' or '2.4
(unreleased)' up to date? It
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
For the Job DSL Plugin [1] we use the Conflunce wiki page only for a
summary and some basic information. For all other documentation we point to
the GitHub wiki [2]. The wiki content is kept in the repo [3], so
contributors can/must update the docs as part of a pull request. To update
the wiki
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
