From 03c9e48f88fa8b681b77c6c35d6da0a0e838a7e8 Mon Sep 17 00:00:00 2001 From: dbrownell Date: Thu, 8 Oct 2009 00:13:50 +0000 Subject: 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 --- testing/smoketests.html | 21 ++++++++++++++++----- 1 file changed, 16 insertions(+), 5 deletions(-) (limited to 'testing/smoketests.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 @@

OpenOCD smoketest results

- 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.

The latest version in which the test is known to have passed is in the table below.

Vocabulary

@@ -282,10 +283,20 @@

Policy on removing features from OpenOCD

- 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. -

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.

+ 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. +

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.

Policy on adding features from OpenOCD

- 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.

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.

ocd4 - ARM7 debugging

@@ -320,4 +331,4 @@

- \ No newline at end of file + -- cgit v1.2.3