Hi, Talkin for myself, you know that I was working on the core version of Linq but it was way too much for me and i gave up on that. Now I am fixing bugs(select one that I can deal from jira and fix) and maybe I will be working on Configuration api(if needed).
My vision: - NHibernate is the .NET port of the excellent Java Hibernate which provides Object/Relational mapping to persist objects in a relational database - we _must_ have our improvements (as we having now), because .net offers different possibilities in some cases which must be taken into consideration. Cheers! On Thu, Nov 6, 2008 at 2:40 PM, Fabio Maulo <[EMAIL PROTECTED]> wrote: > Hi friends.I'm thinking to release NH2.1.0Alpha1 soon but before it I > would like to hear your opinion about your NH vision/future. > My vision: > - > NHibernate is the .NET port of the excellent Java Hibernate which provides > Object/Relational mapping to persist objects in a relational database. > > - we may have our improvements (as we having now) but have the same features > of Hibernate still the target > - I have a list of unsupported features but looking TODO list in code > and/or JIRA is easy to understand how far we are from Hibernate and the > amount of code we need to "review". > > The situation (what I'm seeing): > From 4 or 5 months ago, > NH have 3 new committers to work in NHibernate.Linq project but the project > don't look so "active". > The SVN-Log are showing something about the amount of work of each > committer; btw each one know his situation and his work in NH. > > I would like to know the opinion/vision about NH's future of each > committer. > Please feel free to write what you really want see/do in NH, I'm open to > any solution. > > Thanks. > Fabio Maulo > -- Tuna Toksöz Typos included to enhance the readers attention!
