Yeah, branch the current code path off to a 3.5 branch for critical bug
fixes, move trunk over to 4.0 and increment the major version number so
people who remember to use --safe when updating packages won't get a
breaking version. My production server is still Windows 2003 so .NET 4.5 is
no good fo
I say it's time to let 3.5 pass on and more forward to 4.0/4.5.
On Thursday, December 12, 2013 1:15:53 PM UTC-8, Gleb Chermennov wrote:
>
> Hello everyone, fresh version of Fluent just hit NuGet.
> It's strictly a bugfix release, so please don't expect something glamorous.
> Sorry it's been so lon
There are a couple of bugs in particular that are a thorn in my side. I'd
love to see them fixed. I've never dug into FluentNHibernate before, but
maybe I could help contribute?
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To unsubsc
I'd be fine with .NET 4.0. Everything I have using FluentNHibernate is
.NET 4.0 or .NET 4.5.
--
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 fluent-nhiber
