The release 4.2.0 is closer than ever. With the RC2 and the very short list of release blockers of which most are documentation and confirmation of fixes - things are starting to look very good - and a release is very close.
TWiki has an impressive number of Plugins. Many are now outdated because a better plugin has been made or the core code has adopted the function. But there are at least 100 - maybe close to 200 - that will be relevant to many.
The TWiki plugin repository is one of the major strengths TWiki seen as a project and as a product.
If you are a plugin writer or a plugin user that has tested 4.2 betas or RCs you can make a positive difference to the 4.2 release.
To the plugin writers
With any new release of TWiki there is a risk that your plugin will not work with the new TWiki version for various reasons.
The templates have changed quite a lot so any plugin that contains templates have a potential source of problems. They may work fine but they may also need some tweaks.
Style sheets have changed which may require that you adjust some design
The new Wysiwyg editor may have problems with the syntax your plugin uses. You should check that it all works also after editing and saving with the new
You may have been a bad boy or a bad girl and used internal function calls and not only the Func API. Then for sure things will not work. The Func API has been extended in 4.2.0 so the function you missed may be there now.
But if your plugin is simple and uses only the official API and no special templates then your plugin will most likely still work.
To the general developer community and any users.
If you have been testing the 4.2.0 betas or the Release Candidates and used a plugin - check out the plugin topic on TWiki.org - and make sure the TestedOnTWiki field in the form has 4.2 selected. With several hundreds of plugins it is a great help marking the ones that have been verified to work in 4.2.
If a plugin does not work and you wish it did - raise a bug report on Bugs:WebHome. Even if there already is a request on the plugins Dev page.
Remember that the core developers are normally always very helpful if a plugin you wrote stopped working. It often only takes a small hint to get it going again.