If you simply mark new features with the version number they were/will be introduced in, then users will not be confused by the appearance of a feature in documentation that they do not see in the product. In fact arguably this mode is better for users because they can see what features are scheduled for release, or even have been released already and would be available if they just updated.
Certainly it is more convenient for maintaining FAQs, high-level guides, and so on, as Bobby noted. Detailed documentation of a specific UI element really belongs in the plugin rather than the website anyway. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3ViB5S%2BKRQ4ZCO%3D3dqJ7vGwzvxEQbC83_PNkTfOuJT5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
