Wanted to bring all of you (if any) up to speed with the work I'm doing to make Fluent NHibernate more backwards compatible with earlier version of NH. So far I'm happy with the progress, but there's one thing that keeps bothering me - it's database configuration. Since various dialects are added in parallel with new versions of NH, there's no way I can think of that later versoin of Fluent can be compatible with earlier version of NH if new dialect was added between them - that is, if we don't change public API a little bit. Currently, there's a convenience methods in every Fluent database configuration to use specific dialect - let's say, MsSql.Sql2008(). If we get rid of these methods and ship them as extension methods apart from Fluent release, we'll be able to test virtually every Fluent version with every version of NH. Current test suite should suffice for now, and I'm planning to add end-to-end tests into the mix later. Even more important question - when should I pull this changes off? If it's considered as API breakage, then, following SemVer guidelines, I'll have to wait until 2.0. If not - it can be done in 1.4 release I'm planning in May. Thoughts? Suggestions?
-- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
