The subject of this question speaks for itself. I am wondering if Fluent NHibernate is ready for production code. I am especially wondering in light of some seemingly simple problems that I am having with it that I haven't yet found fully satisfactory solutions for (and the community doesn't have a solution for?)
Why is Fluent NHibernate ignoring my convention?
Why is Fluent NHibernate ignorning my unique constraint on a component?
Yes, I am aware of this old question which is more than a year old; the answer seems to be kinda-sorta-maybe.
Is Fluent NHibernate is ready for production now?
By what metric do you measure "production ready"? How is production any more stringent than other environments? Only you can decide if it meets your needs.
Your first question you have a work around for. Fluent NHibernate is open source, if people aren't dying because of a bug (aka, there's a work around available), it's unlikely our finite resources will be spent on it when there are more important things to be working on. Enums are a known issue, primarily because 50% of people expect them to be mapped as ints, and the others expect strings; either way, one party is going to think that the implementation is a bug.
Your second question looks like a bug. Funnily enough, the Fluent NHibernate developers don't trawl Stack Overflow for possible bugs. If you don't tell us that a bug exists, we won't be able to fix it; sadly, I'm not psychic.
Fluent NHibernate has is past 1.0, which is quite a significant milestone for an OSS project, and is in use in hundreds of production applications. Whether that makes it "production ready" can only be decided by you.
If you don't think it's production ready yet, it's open source and we're always looking for contributors.
This kind of question really should be asked over on their google group page: http://groups.google.com/group/fluent-nhibernate. Being an open source project that is constantly evolving with NHibernate itself, it will almost always be in a semi-flux state, especially with NH3 coming soon.
Do you have unit tests that cover the scope of the functionality of your interaction with Fluent NHibernate? If you do, and they work, then why worry about other features that don't work that you don't use. Besides, a lot of issues with any open source project is lack of understanding of how to use it.
