Next version : NH2.1.0

[Fabio Maulo]

Hi friend.

The time of my "no electricity" vacation is very closer.

Even if we still have something on the Slate

http://groups.google.com/group/nhibernate-development/browse_thread/thread/65a9da3e1f2fc63e

perhaps is the time to take a decision about the next release.

I would like to release NH2.1.0.Alpha1 in May/2009, and then start a 15-days sprints for each release (Alpha2, Beta1, Beta2, RC1, GA).

After Beta2 we can create the 2.1.X branch.

After the creation of the branch we can move NH-Core to NET3.5 and include in the trunk all useful stuff available, so far, in various different prjs.

At that point, IMO, the name of the trunk should be NH-3.0.0 and I hope to include the result of Artorius.

Thoughts ?

--
Fabio Maulo

[Fabio Maulo]

No opinions, in my mind, mean : "I agree with all".

2009/1/8 Fabio Maulo <fabio...@gmail.com>

--
Fabio Maulo

[Tuna Toksöz]

I'll take some stuff from the plate and bake them, when you're off electricity (means that the trunk will be hot).

Artorius the name is cool, lets make it NQF (NHibernate Query Foundation) :) kidding..

What do you have in mind with "usefull stuff available in various diff. projects?"


Tuna Toksöz
http://tunatoksoz.com

Typos included to enhance the readers attention!

[Fabio Maulo]

2009/1/8 Tuna Toksöz <teh...@gmail.com>

What do you have in mind with "usefull stuff available in various diff. projects?"

 

Mean that I'm tired to see a lot of prj extending NH-Core when we can extend it directly in the core it self.

This list is to talk about what is acceptable and what is not but in the last few months even us (committers) are not using the list as expected (expected form me...).

--
Fabio Maulo

[Fabio Maulo]

Sorry Tuna... I must explain something more...

What we wanted to achieve with NH-Contrib and NH-Forge was have a place where NH-Committers and NH-Community may work together and eventually increase the number of committers (well... I mean increase the number of good developers working in NHibernate).

What I saw is projects, piece of code, extensions and so on all "out-side" NHibernate "main-stream".

If a new user would start with NH need a code-hunter to find all useful things to work with NH.

I had accept the situation for prj related with NH but not strictly related to core-stuff (for that I'm not insisting about NHibernate.ApplicationBlock project).

What is more hard to accept, for me, is see extensions and NH-custom-compilation without a single notification to the NH development team (no post here nor JIRA). Well... hard to accept but I know that there is nothing to do... perhaps what we can do is find what is useful and implement it in the trunk directly.

About Artorius : as you know "Artorius" is only the code-name of a future piece of NHibernate core. I start the prj out-side NH only because I would like implement it as a real injectable QueryTranslator without touch, much as possible, the existing code. In Hibernate the AST parser is part of the core and, in some place, you have a "spaghetti-code"; I don't want do the same in NH.

2009/1/8 Fabio Maulo <fabio...@gmail.com>

--
Fabio Maulo

[Davy Brion]

this all sounds pretty good... for NH 3.0 it would also be ok to change some internal stuff right? The whole dealing with parameters thing quickly comes to mind, for instance ;)

--
Davy Brion
http://davybrion.com

[Tuna Toksoz]

@Ayende

I remember you working on Transaction stuff but i don't know the scope, is that the following?

- TransactionStrategy (TransactionFactoryFactory,
TransactionContext, AdoNetContext....)So far talk about NH-Transaction and
talk of Ado.NET transaction, is in practice, the same.
We have a configurable transaction.factory_class but without alternatives.
The target of this work is recreate the same infrastructure of involved
classes H3.2.6 have and allow NH to create and work
with ambient-transactions.

Thanks

Tuna Toksöz
http://tunatoksoz.com

Typos included to enhance the readers attention!

[Ayende Rahien]

NH now works just fine with DTC.

I did not port TransactionContext, the main reason is that in .Net there really isn't the need for that.

There are only two transaction types, local and DTC.

[Tuna Toksoz]

So you say the work is completed for this.
Ok, I'll take jira then :)

Tuna Toksöz
http://tunatoksoz.com

Typos included to enhance the readers attention!