diff options
| author | dbrownell <dbrownell@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-10-08 00:13:50 +0000 |
|---|---|---|
| committer | dbrownell <dbrownell@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-10-08 00:13:50 +0000 |
| commit | 03c9e48f88fa8b681b77c6c35d6da0a0e838a7e8 (patch) | |
| tree | d5410eb810b1409fbb46139caa472460612e5852 /testing | |
| parent | cdc33b38088e6435393b86808b6833d09ea4aa73 (diff) | |
| download | openocd+libswd-03c9e48f88fa8b681b77c6c35d6da0a0e838a7e8.tar.gz openocd+libswd-03c9e48f88fa8b681b77c6c35d6da0a0e838a7e8.tar.bz2 openocd+libswd-03c9e48f88fa8b681b77c6c35d6da0a0e838a7e8.tar.xz openocd+libswd-03c9e48f88fa8b681b77c6c35d6da0a0e838a7e8.zip | |
Change most in-tree references from SVN to GIT.
Also, talk about "mainline" not "trunk".
The release.txt and release.sh files need more updates.
git-svn-id: svn://svn.berlios.de/openocd/trunk@2825 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'testing')
| -rw-r--r-- | testing/index.html | 16 | ||||
| -rw-r--r-- | testing/smoketests.html | 21 |
2 files changed, 27 insertions, 10 deletions
diff --git a/testing/index.html b/testing/index.html index 57085b95..7e5fcb03 100644 --- a/testing/index.html +++ b/testing/index.html @@ -4,10 +4,11 @@ <body> <h1>Release testing</h1> - A release test must be done on code committed to svn. Commit, then test. That way one can know for sure *what* code was actually tested. + A release test must be done on code committed to git. + Commit, then test. That way one can know for sure *what* code was actually tested. <p> Note that this testing document does not have anything to do with testing that is done - before committing to svn. It is a test document for released code. Pre-commit testing + before committing to git. It is a test document for released code. Pre-commit testing is done mostly by the developer who has written the change. Sometimes code is committed to synchronize work, even if it has known problems. Release testing is done on code believed to be stable, often a couple of weeks old, and not by @@ -17,9 +18,14 @@ All of the above makes it imperative that there can be no doubt about *which* code is tested and thus all tests refer to committed code by subversion number. <h1>Release procedure</h1> - OpenOCD trunk is work in progress. Expect it to change daily and to have some quirks. + OpenOCD mainline is work in progress. + Expect it to change daily and to have some quirks. <p>If you need the latest released and tested version, look for binary snapshots of OpenOCD. Worst case look up the test result table below for the features that are important to you and extract and build the version that has the right cocktail of working features for you. You can also work with the community to address the problems you are seing. Testing work and bug reports are highly appreciated.</p> - <p>The OpenOCD community may decide to create release branches. If this happens, then a branch will be created from OpenOCD trunk. The particular version to create that branch might be an older version rather than the latest and greatest. Fixes are then ported to that release branch from OpenOCD trunk.</p> + <p>The OpenOCD community may decide to create release branches. If + this happens, then a branch will be created from OpenOCD mainline. + The particular version to create that branch might be an older version + rather than the latest and greatest. Fixes are then ported to that + release branch from OpenOCD mainline.</p> <hr> <h2>OpenOCD smoketests</h2> This is a set of tests that exercise the entire OpenOCD system and various targets. It @@ -34,4 +40,4 @@ <a href="testcases.html">Test cases</a> </body> -</html>
\ No newline at end of file +</html> diff --git a/testing/smoketests.html b/testing/smoketests.html index 77b22a70..459f8bf6 100644 --- a/testing/smoketests.html +++ b/testing/smoketests.html @@ -4,7 +4,8 @@ <body> <h1>OpenOCD smoketest results</h1> - These tests can be performed on any JTAG device as long as they are executed using the unmodified code from SVN. + These tests can be performed on any JTAG device as long as they are + executed using the unmodified code from git. <p>The latest version in which the test is known to have passed is in the table below.</p> <h2>Vocabulary</h2> <table border="1"> @@ -282,10 +283,20 @@ <p></p> <hr> <h1>Policy on removing features from OpenOCD</h1> - If a feature in OpenOCD is known to be broken and nobody has submitted a fix and the feature is causing trouble for maintainence, it can be removed from OpenOCD trunk. The threshold for temporarily removing something from OpenOCD trunk is low to ease maintainence and place the burden of maintainence on those that care about a feature. - <p>Note that code is never deleted from OpenOCD svn, it remains in svn so if somebody sees a feature removed that they would like kept, they have but to port and fix that feature back up to main trunk. This document can be helpful in this regard in that the latest working version and the known broken version may be listed.</p> + If a feature in OpenOCD is known to be broken and nobody has submitted + a fix and the feature is causing trouble for maintainence, it can be + removed from OpenOCD mainline. The threshold for temporarily removing + something from OpenOCD mainline is low to ease maintainence and place the burden of maintainence on those that care about a feature. + <p>Note that code is never deleted from OpenOCD git, it remains in the + repository so if somebody sees a feature removed that they would like + kept, they have but to port and fix that feature back up to main + mainline. This document can be helpful in this regard in that the latest working version and the known broken version may be listed.</p> <h1>Policy on adding features from OpenOCD</h1> - To add a feature to OpenOCD, generally it should not break any existing features and it should be functional and the code reasonably readable and useful to others in the OpenOCD community. The code does not have to be completed. Work in progress is fine for OpenOCD trunk. + To add a feature to OpenOCD, generally it should not break any + existing features and it should be functional and the code reasonably + readable and useful to others in the OpenOCD community. The code does + not have to be completed. Work in progress is fine for OpenOCD + mainline. <p>Also new tests should be defined. Note that the code does not have to pass all the tests. In fact it can be helpful to have tests to describe facets that really should be working, but aren't done yet. </p> <hr> <h1>ocd4 - ARM7 debugging<a name="test_ocd4"></a></h1> @@ -320,4 +331,4 @@ <p></p> </body> -</html>
\ No newline at end of file +</html> |