[mono-devel-list] Followup on System.Data drop (with Index redesign)
eyala at mainsoft.com
Tue Apr 19 04:52:07 EDT 2005
I have just entered into svn a bundle of new tests for System.Data
disconnected imported from Mainsoft tests.
The tests can be run using nunit and currently we have 36 known failures out
of 319 tests.
We will be working on the failures by integrating Mainsoft's changes to
System.Data disconnected mode into svn as outlined by the process described
Our next step is to send to this dev-list a description of the changes we have
made and to have the changes available for all to review.
---------- Forwarded message ----------
Date: Tue, 12 Apr 2005 11:08:36 -0400
From: Miguel de Icaza <miguel at novell.com>
To: Eyal Alaluf <eyala at mainsoft.com>
Cc: Sureshkumar T <tsureshkumar at novell.com>,
Manjula G H M <mmanjula at novell.com>, borisk <borisk at mainsoft.com>,
Noam Lampert <noaml at mainsoft.com>, Philippe Cohen <philc at mainsoft.com>,
atsushi at ximian.com
Subject: Re: Followup on System.Data drop (with Index redesign)
> I'd like to follow-up on System.Data disconnected drop. Committing
> the improvements of this new source code into mono is a high priority for us -
> it is currently our biggest issue for using Mono's trunk latest directly in
> our builds (and not from our own version control system).
> I'd like to agree upon the best method for doing the above and letting the
> dev-list participlate in the process. The process I'd like to define is:
> * You will do an initial review of the new drop and provide us with
> proposed modifications and raise issues for discussions.
> * We will commit the new source code under a new branch under Mono's svn so
> everyone will have access to the code and can participate in the discussion.
> * We will add into this branch our tests and notify the dev-list on the tests
> additions. (We could also add the tests directly to the trunk, what do you
> * We will then provide the dev-list with a high-level description of the
> modifications as well as the branch name so the sources could be viewed.
> We will then discuss the issues you (Suresh) will raise using the dev-list.
> * We have run already Mono's tests and we found two regressions. Once we
> commit into the branch we will discuss the resolution of these regressions
> over the dev-list (we think that the tests should be modified in this
> case and we definitely would like to discuss this in depth).
> * Once everyone is satisfied with the status of the branch we will merge it
> into the trunk.
> The reason for the above process is that we made a lot of changes that are
> inter-related because of the redesign of DataColumn indices that affected
> a lot of the System.Data disconnected code.
> Please let me know your opinion about this process and if you'd like to
> define another or modify it.
The team in Bangalore and Atsushi are the developers that have been
involved in System.Data, so they have the last word, but Eyal's plan as
outlined above sounds great.
Since Eyal is talking about a branch, we could get the code into the
branch right away so the review can happen in parallel to these
So Eyal's proposal has my OK.
More information about the Mono-devel-list