marking fix in and found in versions to 10.8.1.5 to be merged with 10.8.2 later.

Backported fixes to enable running tests in non-English locale with revision 1157923:
backporting the following revisions to 10.8:
1095247 (DERBY-4260) - derbynet.NetworkServerControlClientCommandTest)
1098033 (DERBY-5211) - tools.SysinfoCPCheckTest
1134139 (DERBY-5252) - lang.GrantRevokeTest
to facilitate testing in non-English locale.
merge commands:
svn merge -c (rev#) https://svn.apache.org/repos/asf/db/derby/code/trunk

Only tested the individual tests modified; there was 1 failure which has happened before on my machine as well as others and so is unrelated:
1) testPingWithWrongHost(org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlClientCommandTest)junit.framework.AssertionFailedError: Could not find expectedString:Unable to find host in output:Mon Aug 15 09:55:36 PDT 2011 : Could not connect to Derby Network Server on host nothere, port 1527: Connection timed out: connect

at org.apache.derbyTesting.junit.BaseTestCase.assertExecJavaCmdAsExpected(BaseTestCase.java:516)
at org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlClientCommandTest.assertFailedPing(NetworkServerControlClientCommandTest.java:147)
at org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlClientCommandTest.testPingWithWrongHost(NetworkServerControlClientCommandTest.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)

backported revision 1128942 for DERBY-5251 (lang.ErrorCodeTest in non-English locale) from trunk to 10.8 with revision 1157937.

Attaching first draft for the release notes for 10.8.2 and a .diff signifying the changes made.

This draft is a bit of a mix between calling this version 10.8.1.6 and 10.8.2, because I've not yet modified the actual version - not in JIRA nor in the source.

There were a couple of issues that tripped me up while generating the release artifacts.

1. ant release complained in svnclean target about local.properties. I am always using this file, rather than $HOME/ ant.properties because I've got multiple branches on the same machine.
I tried moving the local.properties file to a different location, and then using ant -propertyfile, but it doesn't see that. We need to somehow make ant release accept local.properties.

2. ant release would fail in the builduserdocs target, complaining:
-------------------------------
C:\derbyt\108\10.8\build.xml:2711: The following error occurred while executingthis line:
C:\derbyt\108\10.8\build.xml:2052: Execute failed: java.io.IOException: Cannot run program "ant" (in directory "c:\derbyt\108docs\10.8"): CreateProcess error=2,
The system cannot find the file specified.
-------------------------------
This went away when I modified the executable name to ant.bat (and checked it in, or the build would have a 'M' in the version number).
We should either prompt for the ant executable, or figure out how to make this work.
I need to spend a little more time investigating this issue, for when I run in the command line, it finds 'ant.bat' when I issue 'ant'. Perhaps there's something specific to my environment.

3. the build process created a tools/ant/properties/release.properties file with inconsistent line-endings, and as a result, svn commit failed, and as a result of that, the tree was no longer clean and again the build had a version number with 'M'.
I think it might be possible to check for the result from the svn commit, and if failed, prompt the release manager to (a)bort, (c)ontinue. That way, I could open another window and resolve the inconsistent line-endings.
As it was, I took advantage of the setup on my machine that when I click on a dos or cygwin window, it switches to 'text select' mode, which halts the process running in the foreground.

4. ant release automatically set drdamaint version to 0.
In most cases, this would be ok, but we have a special situation with this build where drdamaint needed to be 1 for the fix for DERBY-4236. We should make ant release retain the drdamaint version as is on the branch.

These issues might warrant their own jiras.

I think I finished all the tasks on the list.