Well, I don't know if I can call myself "team" yet, but here's my 2 cents
anyway.
First of all, everything that can be read as criticism in the following
lines should actually be read as "I'm willing to help with that". Here it
goes.
1. It would be important to change the release/support policy, especially if
the mentioned breaking changes are to be included. The current situation is,
there hasn't been a stable, supported NHibernate version for many months
(2.x is not maintained anymore, 3.x is not released yet).
2. While a part of me loves getting rid of legacy libs and using the latest
and coolest stuff, I also know that big companies are usually more
conservative and it will take some time for .NET 4 to be "available" for
everyone (put another way, many companies won't buy VS2010 for their
developers yet). Now, I'm fine with making NH 4.x a .NET4 lib only, *if* 3.x
is kept around and actively maintained (bug fixes; not necessarily new
features)
3. On the more technical side of things, there should be a way to do a
progressive migration from Iesi to .Net 4 ISet<T>. Thinking out loud:
- Add a "default_set_type" to NH Config
- Add types for both, so you can override them one by one
- This essentially means we mean an additional release to get rid of Iesi.
How about deprecating it in 4.x and removing it in 4.5.x or 5.x?
4. On top of this, we really need to do something about documentation. There
are lots of things that are only documented in blogs (all of LINQ, for
example), and many outdated examples and java-isms. I can try to take charge
of this myself, but I need a little help getting started. If anybody wants
to start working with me in this, I have some free time on weekdays before
14 and after 23 UTC; just send me an email.
Diego
On Tue, Oct 12, 2010 at 15:49, Fabio Maulo <[email protected]> wrote:
> Hi *team*.
>
> 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
>
>
