[Oledb-dev] RE: Contributing OLEDB test suite to PostgreSQL
Rafael Mizrahi
rafim at mainsoft.com
Tue Jul 26 10:56:30 GMT 2005
Hi Shachar,
I think that it is best to open the project under the OleDb cvs Under a
Tests directory, since the tests are addressing the OleDb driver.
I will maintain them, but I guess that you will maintain the fixes ;).
Rafi
Mainsoft
-----Original Message-----
From: Shachar Shemesh [mailto:psql at shemesh.biz]
Sent: Tuesday, July 26, 2005 1:03 PM
To: Rafael Mizrahi
Cc: oledb-devel at pgfoundry.org
Subject: Re: Contributing OLEDB test suite to PostgreSQL
Rafael Mizrahi wrote:
>Hi Shachar,
>
>License:
>=============
>Mainsoft also contributes these tests to the mono community,
>http://www.mono-project.com
>So the license is MIT X11
>http://www.opensource.org/licenses/mit-license.html
>MIT X11 is very similar to GPL.
>
>
I'm familiar with it.
>Tests Format:
>=============
>The tests are written in C# and run through the NUnit framework.
>http://www.nunit.org
>I am attaching an example of a Unit test which tests the class DataRow.
>
>Contribution Roadmap:
>=============
>We are still in the process of contributing the tests to the mono
>community,
>We finished contributing all the "DisConnected" tests, and the next
>phase will be to contribute the "Connected" tests.
>
>I wish to open a new project in pgfoundry.org/projects/oledb CVS and
>contribute those "DisConnected" tests, stabilize them, and then, once
we
>will finish the second phase with mono, we will contribute them to
>pgfoundry.org/projects/oledb
>
>What do you think ?
>
>
Is this a case of Mainsoft contributing the code and being done with it,
or do you also wish to maintain it later? The problem with opening a
project under the OleDb cvs is that I lack the skills to maintain such a
project. I am not very familiar with C#, and don't currently even have
the proper compiler installed on my computer.
We can open a new project under CVS, and give your guys commit access to
that project. This means that the driver itself and the the test suites
will share trackers and home page (which is ok, and even a plus).
Alternatively, we can ask pgfoundry for a brand new project just for the
test suites. The main difference between the option is whether you
believe the tests are going to see a lot of activity of their own (bug
fixes, commits, new tests, user questions). If not, then there is no
problem to place it under the oledb hospice. There is also no problem in
integrating with the existing project, and splitting it if/when it
becomes relevant.
So, to sum it up, you want to give unit tests for PgOleDb under the X11
license. I still need to know whether you will be maintaining it after
initial release, or whether we shall have to seek a maintainer that
knows C# and .NET for them.
>Rafi
>Mainsoft
>
>
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting ltd.
http://www.lingnu.com/
More information about the Oledb-devel
mailing list