If a new release is coming, would it be possible to apply the patch from https://nhibernate.jira.com/browse/NH-2905 ? I'm currently using my own build of 3.2.0 with that patch applied because such queries are needed in the application I'm working on. But it would be great if no own builds would be required so that other persons working on that application (that have no knowledge of NHibernate code) could update NHibernate too.
On 12 Okt., 17:18, Patrick Earl <[email protected]> wrote: > I think it would be good to release. > > Patrick Earl > > > > > > > > On Wed, Oct 12, 2011 at 8:02 AM, Stephen Bohlen <[email protected]> wrote: > > Probably. What is the consensus? Are we ready to release 3.2.1 as of now > > or not --? > > > Steve Bohlen > > [email protected] > >http://blog.unhandled-exceptions.com > >http://twitter.com/sbohlen > > > On Wed, Oct 12, 2011 at 9:47 AM, Richard Brown (gmail) > > <[email protected]> wrote: > > >> I see that Julian has fixed a (high priority IMHO) problem that affects > >> several different platforms: https://nhibernate.jira.com/browse/NH-2893 > > >> Should we revisit releasing 3.2.1? > > >> From: sbohlen > >> Sent: Wednesday, August 17, 2011 11:55 AM > >> To: [email protected] > >> Subject: Re: [nhibernate-development] NH3.2.1 > >> Just wondering if anyone can provide a clarification on the status of what > >> we're planning to do with this (?) It seemed that initially there was some > >> urgency around trying to rapidly release a 3.2.1GA to get this modification > >> officially out there for people but then this thread has sat idle for 8+ > >> days now. The issue shows RESOLVED so we should be clear to release a > >> 3.2.1GA at this point AFAIK. Are there other blockers preventing this at > >> this point that need attention or is it possible to proceed with the > >> release > >> now? > > >> (concerned for the performance implications of having this issue present > >> in our latest 'official' release out there for adopters) > > >> Thoughts --? > > >> -Steve B.
