+1 On Wed, Oct 13, 2010 at 12:30 PM, Valeriu Caraulean <[email protected]>wrote:
> I would really appreciate having a "native" fluent/code mapping solution, > that is coming together with NHibernate. > > On Tue, Oct 12, 2010 at 8:49 PM, Fabio Maulo <[email protected]> wrote: > >> Hi *team*. >> > > You're not restricting *who *wants/can to give opinions, right? > > > >> >> You have around 30 days to talk with people to have some ideas about what >> each one is thinking about NH next. >> The main matter is not about improvements, features or issues in general >> but about the "other" big JUMP. >> Perhaps after 3.0.0, this time, we may wait a little bit before open the >> 3.x branch and start developing NH4... >> Perhaps we have to plan only a little minor release after 3.0.0GA... >> something like one month or month and half to release 3.0.1 with some bug >> fix. >> >> Personally I would release NH4.0.0 very quickly with one mayor >> change: Remove Iesi.Collection (sig) for external usage... >> That mean (phase1): >> 1) a separated ICollectionTypeFactory for back draw compatibility and to >> give the opportunity to convert existing projects >> 2) Adios no strongly typed <set> (no Iesi ? well... only the ISet<T> will >> be supported) >> 3) The <set> will mean .Net4 ISet<T> by default >> 4) No more support for .NET3.5 >> >> (phase2) >> After NH4.0.0 we can start the real hard work but it will be "only" >> internal... the remotion of the reference to Iesi.Collection >> We may walk some others routes but I prefer a drastic cut instead a long >> torture. >> >> During phase2 I would implements some others ideas but that will be matter >> of appropriate discussions. >> >> The other possibility is to give support to both (Iesi and .Net) >> ISet differentiating it through a specific <type>... in any case it mean: >> bye bye .NET3.5 >> >> Please try to avoid a quick answer and take your time to "digest" the >> matter. >> >> -- >> Fabio Maulo >> >> >
