Sorry -- hit SEND by accident there ;) What I was *trying* to say... If there are significant bug-fixes that we believe to be blockers for adoption in 3.3.1 then I'd say its worth looking at a 3.3.2 release. However, in the past this project hasn't (usually) seen more than a single release after N.N.0 (e.g., an N.N.1 but only very rarely an N.N.2 release). In general fewer, stable releases have been preferred over more frequent releases. I don't know that this has been an actual point of past discussion, but it seems to me that given the number of co-dependent projects (nhcontrib, and beyond) its *generally* been preferable not to "release early and often" because of the corresponding need to update the rest of the 'ecosystem' that takes NH as a dependency.
Did you have a specific one (or more) bug-fixes in mind that are critical enough to warrant an earlier release prior to 4.0 (or even a 3.4?) I've noticed activity around several issues re: the LINQ provider (now resolved) that appear to be fixed -- was that what you had in mind to get out there in an official release? Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Wed, Jul 25, 2012 at 8:25 AM, Stephen Bohlen <[email protected]> wrote: > > Steve Bohlen > [email protected] > http://blog.unhandled-exceptions.com > http://twitter.com/sbohlen > > > > On Wed, Jul 25, 2012 at 7:51 AM, Moisés Gonçalves <[email protected]>wrote: > >> Isn’t it too early to generate another version?**** >> >> ** ** >> >> *De:* [email protected] [mailto: >> [email protected]] *Em nome de *Alexander I. >> Zaytsev >> *Enviada em:* terça-feira, 24 de julho de 2012 12:42 >> *Para:* [email protected] >> *Assunto:* [nhibernate-development] NH 3.3.2**** >> >> ** ** >> >> Hello everyone.**** >> >> ** ** >> >> There are some minor bug fixes and imporvements. I was thought that I >> could prepare 3.3.2 release and then we could deliver it. **** >> >> ** ** >> >> What do you think?**** >> >> ** ** >> >> Best Regards, Alex.**** >> > >
