[Mono-list] RE: [Mono-devel-list] Mono Roadmap ready.

Miguel de Icaza miguel@ximian.com
05 Nov 2003 22:12:46 -0500


Hello,
	
> Here are my thoughts on the roadmap to Mono-1.0:
> 
> What about ICSharpCode.SharpZipLib?
> Its a third-party assembly, but it is required by ByteFX.Data MySQLClient
> and other things.
> Does monodoc depend on SharpZipLib?

Ah, good point.  This should be made part of the 1.0 third-party set.

> The following assemblies are deprecated and I thus should be removed from
> cvs since no has worked on them in a long time.  They have 100% C#
> implementations.
> 
> ono.Data.PostgreSqlClient
> Mono.Data.MySql

I can remove them from CVS if you want to.

> I would not consider Mono.Data.TdsClient as being stable since it was
> created for older Sybase and Microsoft SQL Server databases.  Mono.Data.Tds
> is another story - it does work well.

Thanks for the data points, I have updated the roadmap with these bits.

Miguel
> 
> Mono.Data which includes the ProviderFactory is stable for me.  There are
> some enhacements to it that I would like to do.  I use the ProviderFactory
> within Mono and .net projects.
> 
> Daniel
> 
> -----Original Message-----
> From: mono-devel-list-admin@lists.ximian.com
> [mailto:mono-devel-list-admin@lists.ximian.com]On Behalf Of Miguel de
> Icaza
> Sent: Tuesday, November 04, 2003 10:27 AM
> To: mono-list@ximian.com; mono-devel-list@ximian.com; Mono Announce
> Subject: [Mono-devel-list] Mono Roadmap ready.
> 
> 
> Hello,
> 
>     The Mono project roadmap is now available:
> 
> 	http://www.go-mono.com/mono-roadmap.html
> 
>     A roadmap for contributors:
> 
> 	http://www.go-mono.com/mono-hacking-roadmap.html
> 
> Miguel
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
-- 
Miguel de Icaza <miguel@ximian.com>