You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rick Hillegas <ri...@gmail.com> on 2015/09/26 21:54:26 UTC

testing 10.12.1.1

Thanks for everyone's help so far in testing 10.12.1.1. There are still 
some untested checklist items at 
http://wiki.apache.org/db-derby/TenTwelveOneChecklist. Also, it would be 
good to see some more platform test results at 
http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting.

Thanks!
-Rick

Re: testing 10.12.1.1

Posted by mike matrigali <mi...@gmail.com>.
I am unlikely to have time to help, but wanted to mention a few things:

I don't think we have done the following for multiple releases:
upgrade and compatibility (ask Kathey)  - I think it involved running a past test jar against
a current release jar and looking at the failures.  When a lot of stuff was going into the release
the took weeks of effort and mostly were "acceptable" failures where different error messages were
thrown now vs before.

Knut did a test by hand that I thought was valuable, but not sure how he did it.  He took a db built
at previous release level and then ran full set of current built test jars vs current db.  Not sure if
he did soft upgrade or hard upgrade or both.  The good catches were identifying places where new
code did not understand the format on disk of old stuff.  i think the issue was always stored plan
related and the fix was just to make sure that the new release caused the problem thing on disk to
be invalidate and rebuilt.

On 9/26/2015 12:54 PM, Rick Hillegas wrote:
> Thanks for everyone's help so far in testing 10.12.1.1. There are still some untested checklist items at 
> http://wiki.apache.org/db-derby/TenTwelveOneChecklist. Also, it would be good to see some more platform test results at 
> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting.
>
> Thanks!
> -Rick
>


-- 
email:    Mike Matrigali - mikemapp1@gmail.com
linkedin: https://www.linkedin.com/in/MikeMatrigali


Re: testing 10.12.1.1

Posted by Rick Hillegas <ri...@gmail.com>.
Hi Alex,

These results look like some kind of environmental problem. Maybe you 
can try, for instance, running one of the JUnit tests by itself and 
forward the complete console output.

Thanks,
-Rick

On 9/30/15 11:09 AM, Alex wrote:
> Rick,
> I ran the tests - there are some failures, attaching outputs.
>
> /--Regards, Alex/
>
> ------------------------------------------------------------------------
>
> *From:* Alex
> *Sent:* Tuesday, September 29, 2015 5:55PM
> *To:* Derby-dev
> *Subject:* Re: testing 10.12.1.1
>> Hi Rick,
>>> After a successful vote on a RC, the release manager tags it and 
>>> publishes it. This is step 4 near the bottom of this webpage: 
>>> http://wiki.apache.org/db-derby/ReleasePublication. Until then, the 
>>> RC is identified merely by its subversion commit stamp (which you 
>>> can view by running org.apache.derby.tools.sysinfo).
>> Thanks. I don't see any 10.12-rc tags at 
>> https://svn.apache.org/repos/asf/db/derby/code/tags/ though.
>>> A test coverage run on RC2 would be sufficient I think.
>>> RC2 is available here: http://people.apache.org/~rhillegas/10.12.1.1/
>> OK, I will run tests on that. It's a little odd that rc has to be 
>> obtained from somewhere outside VCS, instead of updating working 
>> directory to a particular (tagged e.g. "10.12.1.1-RC2") commit.
>>
>> /--Regards, Alex/
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Rick Hillegas
>> *Sent:* Tuesday, September 29, 2015 4:41PM
>> *To:* Alex, Derby-dev
>> *Subject:* Re: testing 10.12.1.1
>>> Hi Alex,
>>>
>>> I'm moving this conversation to the dev list because I think other 
>>> people may be interested in the discussion. Some responses inline...
>>>
>>> On 9/29/15 12:54 AM, Alex wrote:
>>>> Ok, ant testing targets are working. This is much simpler than the 
>>>> process described here 
>>>> http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/README.htm?view=co 
>>>> :)
>>>>
>>>> How do you mark RC's in svn?
>>> After a successful vote on a RC, the release manager tags it and 
>>> publishes it. This is step 4 near the bottom of this webpage: 
>>> http://wiki.apache.org/db-derby/ReleasePublication. Until then, the 
>>> RC is identified merely by its subversion commit stamp (which you 
>>> can view by running org.apache.derby.tools.sysinfo).
>>>> I can't find any tags in the repository. It looks like both RC1 and 
>>>> RC2 need test coverage atm 
>>>> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting
>>> A test coverage run on RC2 would be sufficient I think.
>>>> I checked out 10.12 branch from here 
>>>> https://svn.apache.org/repos/asf/db/derby/code/branches/10.12, how 
>>>> do I switch between RC's?
>>> Technically, you aren't testing the RC if you are building from the 
>>> branch. The RC is the set of distros built by the release manager 
>>> and announced when the release manager calls for a vote. At this 
>>> point, I have deleted RC1. RC2 is available here: 
>>> http://people.apache.org/~rhillegas/10.12.1.1/
>>>
>>> If you need to set your branch to a particular commit stamp, you can 
>>> use the following subversion command:
>>>
>>> svn checkout -r $revisionStamp
>>>
>>> Maybe someone else kept a copy of RC1 and can use sysinfo to extract 
>>> its subversion commit stamp. According to the history on 
>>> https://issues.apache.org/jira/browse/DERBY-6811, the version id on 
>>> the 10.12 branch was bumped to 10.12.1.1 by revision r1702842. That 
>>> happened just after RC1 was generated. So if you set the revision 
>>> stamp to 1702841, that would be pretty close to the definition of RC1.
>>>
>>> Thanks,
>>> -Rick
>>>>
>>>> /--Regards, Alex/
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> *From:* Rick Hillegas
>>>> *Sent:* Tuesday, September 29, 2015 3:54AM
>>>> *To:* Alex
>>>> *Subject:* Re: testing 10.12.1.1
>>>> Not sure what's going on. Have you tried running the tests like 
>>>> this (these targets should set up the classpath for you):
>>>>
>>>> ant test-derbyall
>>>>
>>>> ant junit-all
>>>>
>>>> Thanks,
>>>> -Rick
>>>>
>>>> On 9/28/15 3:56 AM, Alex wrote:
>>>>> I compiled the trunk (including derbyTesting.jar), but I'm having 
>>>>> a problem running tests. According to tests readme, I'm doing the 
>>>>> following (Java positively refuses to pick up my CLASSPATH shell 
>>>>> variable, hence -classpath):
>>>>>
>>>>> java -Dverbose=true -classpath 
>>>>> /home/username/.javabin/jakarta-oro-2.0.8.jar:/usr/share/java/junit.jar:/home/username/code/derby/jars/sane/* 
>>>>> org.apache.derbyTesting.functionTests.harness.RunSuite encodingTests
>>>>>
>>>>> It stumbles on derbytools (report files attached):
>>>>> Error: Could not find or load main class 
>>>>> org.apache.derby.tools.sysinfo
>>>>>
>>>>> Can't find anything related in mail list archives, any suggestions?
>>>>>
>>>>> /--Regards, Alex/
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> *From:* Rick Hillegas
>>>>> *Sent:* Sunday, September 27, 2015 5:23PM
>>>>> *To:* Alex
>>>>> *Subject:* Re: testing 10.12.1.1
>>>>> Hi Alex,
>>>>>
>>>>> Everyone is welcome to kick the tires. The more platform coverage 
>>>>> the better.
>>>>>
>>>>> Thanks!
>>>>> -Rick
>>>>>
>>>>> On 9/26/15 3:31 PM, Alex wrote:
>>>>>> Hello Rick,
>>>>>> Is this intended only for Derby developers, or users as well?
>>>>>> I would gladly help out with the tests (I'm on Linux and it isn't 
>>>>>> covered yet).
>>>>>>
>>>>>> /--Regards, Alex/
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>> *From:* Rick Hillegas
>>>>>> *Sent:* Saturday, September 26, 2015 10:54PM
>>>>>> *To:* Derby-dev
>>>>>> *Subject:* testing 10.12.1.1
>>>>>> Thanks for everyone's help so far in testing 10.12.1.1. There are 
>>>>>> still some untested checklist items at 
>>>>>> http://wiki.apache.org/db-derby/TenTwelveOneChecklist. Also, it 
>>>>>> would be good to see some more platform test results at 
>>>>>> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting.
>>>>>>
>>>>>> Thanks!
>>>>>> -Rick
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>


Re: testing 10.12.1.1

Posted by Alex <al...@zoho.com>.
Rick,
I ran the tests - there are some failures, attaching outputs.

/--Regards, Alex/

------------------------------------------------------------------------

*From:* Alex
*Sent:* Tuesday, September 29, 2015 5:55PM
*To:* Derby-dev
*Subject:* Re: testing 10.12.1.1
> Hi Rick,
>> After a successful vote on a RC, the release manager tags it and 
>> publishes it. This is step 4 near the bottom of this webpage: 
>> http://wiki.apache.org/db-derby/ReleasePublication. Until then, the 
>> RC is identified merely by its subversion commit stamp (which you can 
>> view by running org.apache.derby.tools.sysinfo).
> Thanks. I don't see any 10.12-rc tags at 
> https://svn.apache.org/repos/asf/db/derby/code/tags/ though.
>> A test coverage run on RC2 would be sufficient I think.
>> RC2 is available here: http://people.apache.org/~rhillegas/10.12.1.1/
> OK, I will run tests on that. It's a little odd that rc has to be 
> obtained from somewhere outside VCS, instead of updating working 
> directory to a particular (tagged e.g. "10.12.1.1-RC2") commit.
>
> /--Regards, Alex/
>
> ------------------------------------------------------------------------
>
> *From:* Rick Hillegas
> *Sent:* Tuesday, September 29, 2015 4:41PM
> *To:* Alex, Derby-dev
> *Subject:* Re: testing 10.12.1.1
>> Hi Alex,
>>
>> I'm moving this conversation to the dev list because I think other 
>> people may be interested in the discussion. Some responses inline...
>>
>> On 9/29/15 12:54 AM, Alex wrote:
>>> Ok, ant testing targets are working. This is much simpler than the 
>>> process described here 
>>> http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/README.htm?view=co 
>>> :)
>>>
>>> How do you mark RC's in svn?
>> After a successful vote on a RC, the release manager tags it and 
>> publishes it. This is step 4 near the bottom of this webpage: 
>> http://wiki.apache.org/db-derby/ReleasePublication. Until then, the 
>> RC is identified merely by its subversion commit stamp (which you can 
>> view by running org.apache.derby.tools.sysinfo).
>>> I can't find any tags in the repository. It looks like both RC1 and 
>>> RC2 need test coverage atm 
>>> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting
>> A test coverage run on RC2 would be sufficient I think.
>>> I checked out 10.12 branch from here 
>>> https://svn.apache.org/repos/asf/db/derby/code/branches/10.12, how 
>>> do I switch between RC's?
>> Technically, you aren't testing the RC if you are building from the 
>> branch. The RC is the set of distros built by the release manager and 
>> announced when the release manager calls for a vote. At this point, I 
>> have deleted RC1. RC2 is available here: 
>> http://people.apache.org/~rhillegas/10.12.1.1/
>>
>> If you need to set your branch to a particular commit stamp, you can 
>> use the following subversion command:
>>
>> svn checkout -r $revisionStamp
>>
>> Maybe someone else kept a copy of RC1 and can use sysinfo to extract 
>> its subversion commit stamp. According to the history on 
>> https://issues.apache.org/jira/browse/DERBY-6811, the version id on 
>> the 10.12 branch was bumped to 10.12.1.1 by revision r1702842. That 
>> happened just after RC1 was generated. So if you set the revision 
>> stamp to 1702841, that would be pretty close to the definition of RC1.
>>
>> Thanks,
>> -Rick
>>>
>>> /--Regards, Alex/
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Rick Hillegas
>>> *Sent:* Tuesday, September 29, 2015 3:54AM
>>> *To:* Alex
>>> *Subject:* Re: testing 10.12.1.1
>>> Not sure what's going on. Have you tried running the tests like this 
>>> (these targets should set up the classpath for you):
>>>
>>> ant test-derbyall
>>>
>>> ant junit-all
>>>
>>> Thanks,
>>> -Rick
>>>
>>> On 9/28/15 3:56 AM, Alex wrote:
>>>> I compiled the trunk (including derbyTesting.jar), but I'm having a 
>>>> problem running tests. According to tests readme, I'm doing the 
>>>> following (Java positively refuses to pick up my CLASSPATH shell 
>>>> variable, hence -classpath):
>>>>
>>>> java -Dverbose=true -classpath 
>>>> /home/username/.javabin/jakarta-oro-2.0.8.jar:/usr/share/java/junit.jar:/home/username/code/derby/jars/sane/* 
>>>> org.apache.derbyTesting.functionTests.harness.RunSuite encodingTests
>>>>
>>>> It stumbles on derbytools (report files attached):
>>>> Error: Could not find or load main class org.apache.derby.tools.sysinfo
>>>>
>>>> Can't find anything related in mail list archives, any suggestions?
>>>>
>>>> /--Regards, Alex/
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> *From:* Rick Hillegas
>>>> *Sent:* Sunday, September 27, 2015 5:23PM
>>>> *To:* Alex
>>>> *Subject:* Re: testing 10.12.1.1
>>>> Hi Alex,
>>>>
>>>> Everyone is welcome to kick the tires. The more platform coverage 
>>>> the better.
>>>>
>>>> Thanks!
>>>> -Rick
>>>>
>>>> On 9/26/15 3:31 PM, Alex wrote:
>>>>> Hello Rick,
>>>>> Is this intended only for Derby developers, or users as well?
>>>>> I would gladly help out with the tests (I'm on Linux and it isn't 
>>>>> covered yet).
>>>>>
>>>>> /--Regards, Alex/
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>> *From:* Rick Hillegas
>>>>> *Sent:* Saturday, September 26, 2015 10:54PM
>>>>> *To:* Derby-dev
>>>>> *Subject:* testing 10.12.1.1
>>>>> Thanks for everyone's help so far in testing 10.12.1.1. There are 
>>>>> still some untested checklist items at 
>>>>> http://wiki.apache.org/db-derby/TenTwelveOneChecklist. Also, it 
>>>>> would be good to see some more platform test results at 
>>>>> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting.
>>>>>
>>>>> Thanks!
>>>>> -Rick
>>>>>
>>>>
>>>>
>>>
>>>
>>
>


Re: testing 10.12.1.1

Posted by Alex <al...@zoho.com>.
Hi Rick,
> After a successful vote on a RC, the release manager tags it and 
> publishes it. This is step 4 near the bottom of this webpage: 
> http://wiki.apache.org/db-derby/ReleasePublication. Until then, the RC 
> is identified merely by its subversion commit stamp (which you can 
> view by running org.apache.derby.tools.sysinfo).
Thanks. I don't see any 10.12-rc tags at 
https://svn.apache.org/repos/asf/db/derby/code/tags/ though.
> A test coverage run on RC2 would be sufficient I think.
> RC2 is available here: http://people.apache.org/~rhillegas/10.12.1.1/
OK, I will run tests on that. It's a little odd that rc has to be 
obtained from somewhere outside VCS, instead of updating working 
directory to a particular (tagged e.g. "10.12.1.1-RC2") commit.

/--Regards, Alex/

------------------------------------------------------------------------

*From:* Rick Hillegas
*Sent:* Tuesday, September 29, 2015 4:41PM
*To:* Alex, Derby-dev
*Subject:* Re: testing 10.12.1.1
> Hi Alex,
>
> I'm moving this conversation to the dev list because I think other 
> people may be interested in the discussion. Some responses inline...
>
> On 9/29/15 12:54 AM, Alex wrote:
>> Ok, ant testing targets are working. This is much simpler than the 
>> process described here 
>> http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/README.htm?view=co 
>> :)
>>
>> How do you mark RC's in svn?
> After a successful vote on a RC, the release manager tags it and 
> publishes it. This is step 4 near the bottom of this webpage: 
> http://wiki.apache.org/db-derby/ReleasePublication. Until then, the RC 
> is identified merely by its subversion commit stamp (which you can 
> view by running org.apache.derby.tools.sysinfo).
>> I can't find any tags in the repository. It looks like both RC1 and 
>> RC2 need test coverage atm 
>> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting
> A test coverage run on RC2 would be sufficient I think.
>> I checked out 10.12 branch from here 
>> https://svn.apache.org/repos/asf/db/derby/code/branches/10.12, how do 
>> I switch between RC's?
> Technically, you aren't testing the RC if you are building from the 
> branch. The RC is the set of distros built by the release manager and 
> announced when the release manager calls for a vote. At this point, I 
> have deleted RC1. RC2 is available here: 
> http://people.apache.org/~rhillegas/10.12.1.1/
>
> If you need to set your branch to a particular commit stamp, you can 
> use the following subversion command:
>
> svn checkout -r $revisionStamp
>
> Maybe someone else kept a copy of RC1 and can use sysinfo to extract 
> its subversion commit stamp. According to the history on 
> https://issues.apache.org/jira/browse/DERBY-6811, the version id on 
> the 10.12 branch was bumped to 10.12.1.1 by revision r1702842. That 
> happened just after RC1 was generated. So if you set the revision 
> stamp to 1702841, that would be pretty close to the definition of RC1.
>
> Thanks,
> -Rick
>>
>> /--Regards, Alex/
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Rick Hillegas
>> *Sent:* Tuesday, September 29, 2015 3:54AM
>> *To:* Alex
>> *Subject:* Re: testing 10.12.1.1
>> Not sure what's going on. Have you tried running the tests like this 
>> (these targets should set up the classpath for you):
>>
>> ant test-derbyall
>>
>> ant junit-all
>>
>> Thanks,
>> -Rick
>>
>> On 9/28/15 3:56 AM, Alex wrote:
>>> I compiled the trunk (including derbyTesting.jar), but I'm having a 
>>> problem running tests. According to tests readme, I'm doing the 
>>> following (Java positively refuses to pick up my CLASSPATH shell 
>>> variable, hence -classpath):
>>>
>>> java -Dverbose=true -classpath 
>>> /home/username/.javabin/jakarta-oro-2.0.8.jar:/usr/share/java/junit.jar:/home/username/code/derby/jars/sane/* 
>>> org.apache.derbyTesting.functionTests.harness.RunSuite encodingTests
>>>
>>> It stumbles on derbytools (report files attached):
>>> Error: Could not find or load main class org.apache.derby.tools.sysinfo
>>>
>>> Can't find anything related in mail list archives, any suggestions?
>>>
>>> /--Regards, Alex/
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Rick Hillegas
>>> *Sent:* Sunday, September 27, 2015 5:23PM
>>> *To:* Alex
>>> *Subject:* Re: testing 10.12.1.1
>>> Hi Alex,
>>>
>>> Everyone is welcome to kick the tires. The more platform coverage 
>>> the better.
>>>
>>> Thanks!
>>> -Rick
>>>
>>> On 9/26/15 3:31 PM, Alex wrote:
>>>> Hello Rick,
>>>> Is this intended only for Derby developers, or users as well?
>>>> I would gladly help out with the tests (I'm on Linux and it isn't 
>>>> covered yet).
>>>>
>>>> /--Regards, Alex/
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> *From:* Rick Hillegas
>>>> *Sent:* Saturday, September 26, 2015 10:54PM
>>>> *To:* Derby-dev
>>>> *Subject:* testing 10.12.1.1
>>>> Thanks for everyone's help so far in testing 10.12.1.1. There are 
>>>> still some untested checklist items at 
>>>> http://wiki.apache.org/db-derby/TenTwelveOneChecklist. Also, it 
>>>> would be good to see some more platform test results at 
>>>> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting.
>>>>
>>>> Thanks!
>>>> -Rick
>>>>
>>>
>>>
>>
>>
>


Re: testing 10.12.1.1

Posted by Rick Hillegas <ri...@gmail.com>.
Hi Alex,

I'm moving this conversation to the dev list because I think other 
people may be interested in the discussion. Some responses inline...

On 9/29/15 12:54 AM, Alex wrote:
> Ok, ant testing targets are working. This is much simpler than the 
> process described here 
> http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/README.htm?view=co 
> :)
>
> How do you mark RC's in svn?
After a successful vote on a RC, the release manager tags it and 
publishes it. This is step 4 near the bottom of this webpage: 
http://wiki.apache.org/db-derby/ReleasePublication. Until then, the RC 
is identified merely by its subversion commit stamp (which you can view 
by running org.apache.derby.tools.sysinfo).
> I can't find any tags in the repository. It looks like both RC1 and 
> RC2 need test coverage atm 
> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting
A test coverage run on RC2 would be sufficient I think.
> I checked out 10.12 branch from here 
> https://svn.apache.org/repos/asf/db/derby/code/branches/10.12, how do 
> I switch between RC's?
Technically, you aren't testing the RC if you are building from the 
branch. The RC is the set of distros built by the release manager and 
announced when the release manager calls for a vote. At this point, I 
have deleted RC1. RC2 is available here: 
http://people.apache.org/~rhillegas/10.12.1.1/

If you need to set your branch to a particular commit stamp, you can use 
the following subversion command:

svn checkout -r $revisionStamp

Maybe someone else kept a copy of RC1 and can use sysinfo to extract its 
subversion commit stamp. According to the history on 
https://issues.apache.org/jira/browse/DERBY-6811, the version id on the 
10.12 branch was bumped to 10.12.1.1 by revision r1702842. That happened 
just after RC1 was generated. So if you set the revision stamp to 
1702841, that would be pretty close to the definition of RC1.

Thanks,
-Rick
>
> /--Regards, Alex/
>
> ------------------------------------------------------------------------
>
> *From:* Rick Hillegas
> *Sent:* Tuesday, September 29, 2015 3:54AM
> *To:* Alex
> *Subject:* Re: testing 10.12.1.1
> Not sure what's going on. Have you tried running the tests like this 
> (these targets should set up the classpath for you):
>
> ant test-derbyall
>
> ant junit-all
>
> Thanks,
> -Rick
>
> On 9/28/15 3:56 AM, Alex wrote:
>> I compiled the trunk (including derbyTesting.jar), but I'm having a 
>> problem running tests. According to tests readme, I'm doing the 
>> following (Java positively refuses to pick up my CLASSPATH shell 
>> variable, hence -classpath):
>>
>> java -Dverbose=true -classpath 
>> /home/username/.javabin/jakarta-oro-2.0.8.jar:/usr/share/java/junit.jar:/home/username/code/derby/jars/sane/* 
>> org.apache.derbyTesting.functionTests.harness.RunSuite encodingTests
>>
>> It stumbles on derbytools (report files attached):
>> Error: Could not find or load main class org.apache.derby.tools.sysinfo
>>
>> Can't find anything related in mail list archives, any suggestions?
>>
>> /--Regards, Alex/
>>
>> ------------------------------------------------------------------------
>>
>> *From:* Rick Hillegas
>> *Sent:* Sunday, September 27, 2015 5:23PM
>> *To:* Alex
>> *Subject:* Re: testing 10.12.1.1
>> Hi Alex,
>>
>> Everyone is welcome to kick the tires. The more platform coverage the 
>> better.
>>
>> Thanks!
>> -Rick
>>
>> On 9/26/15 3:31 PM, Alex wrote:
>>> Hello Rick,
>>> Is this intended only for Derby developers, or users as well?
>>> I would gladly help out with the tests (I'm on Linux and it isn't 
>>> covered yet).
>>>
>>> /--Regards, Alex/
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* Rick Hillegas
>>> *Sent:* Saturday, September 26, 2015 10:54PM
>>> *To:* Derby-dev
>>> *Subject:* testing 10.12.1.1
>>> Thanks for everyone's help so far in testing 10.12.1.1. There are 
>>> still some untested checklist items at 
>>> http://wiki.apache.org/db-derby/TenTwelveOneChecklist. Also, it 
>>> would be good to see some more platform test results at 
>>> http://wiki.apache.org/db-derby/TenTwelveOnePlatformTesting.
>>>
>>> Thanks!
>>> -Rick
>>>
>>
>>
>
>