As long as Fluent NHibernate comes with NHibernate and its clearly noted as being version NH 3.0 then I think that's enough.
After downloading people, that are 'in the know', can replace the NHibernate files with 3.X.Y if needed. Also, if it FNH defaults to Castle and removes the hurdle of when you would choose linfu over castle, it makes things even easier to get started for a newcomer. On Wed, Dec 8, 2010 at 11:12 AM, James Gregory <[email protected]>wrote: > This is the first I've heard of anyone being confused by our version > numbers... > > In my opinion this is an education issue, not something that should be > solved by altering our version numbers. We're an independent project and our > release cycles are not tied to NH. > > FNH 1.0 was compatible with 1.2 and 2.1 of NHibernate, 1.1 compatible with > 2.1, 1.2 compatible with 2.1 and 3.0, and 2.0 will be compatible with 3.0 > upwards; I don't see an easy way to indicate that in our version numbers > without compromising our ability to version independently from NHibernate > *and* maintain the intention of version numbers (major number changes > indicate breaking changes, minor indicates fixes but binary compatibility). > > It should be made clearer on the website when you're downloading FNH what > version of NHibernate it's compatible with. > > -- > You received this message because you are subscribed to the Google Groups > "Fluent NHibernate" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<fluent-nhibernate%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/fluent-nhibernate?hl=en. > -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
