Something seems to be amiss with the SVN scheme.
- If a user wants to apply the standard tests to their installation or wants to develop plugins using tests of the most recent release, such user must install the release via SVN as some of the necessary code (e.g., the test platform) are not easily obtained via downloads.
- However, per the list of tags, http://svn.twiki.org/svn/twiki/branches/, there is no way of checking out the current release 4.1.2
Consequentially, we either should provide always a way of checking out the latest release from SVN, or we should provide all artifacts (e.g., unit tests, testing framework) via downloads in addition to SVN checkout.
The tagged releases are in the tags part of SVN.
But then you get the frozen version from that release so that is not recommended.
Plugin developers should check out the MAIN branch and the current release branch if they want to test their plugins using the most up to date unit test beds.
But if they just want to test a plugin manually (most will I am sure because the unit test stuff is for the real experts. I personally understand nothing anymore when it comes to unit tests) then testing in the branch of the current shipping release is also pretty good. That branch is http://svn.twiki.org/svn/twiki/branches/Patch04x01/
In Rome it was decided that from 4.2 the name changes from PatchXXxXX to TWikiReleaseXXxXX.
There are talks at the moment of how we can separate the plugins that are not shipped with TWiki in their own branch that can be used with any core branch.
Until then ALL checkins of plugins that are developed on SVN must be checked into MAIN. It is OK to check them in to the other branches to help testing but it is always the version in MAIN that is regarded the current valid version on SVN.