Nice joke, Ricardo

cremor, because I did not look there carefully. The 4.0.2 release was
prepared a month ago or so, I just did not have time to build and make
release notes.

Best Regards,
Alexander

On Mon, Nov 17, 2014 at 10:34 PM, Ricardo Peres <[email protected]> wrote:

> It probably didn't have the "fix version" set, so it slipped!
>
> RP
>
>
> On Monday, November 17, 2014 6:46:24 AM UTC, cremor wrote:
>>
>> What prevented NH-3731 <https://nhibernate.jira.com/browse/NH-3731> (PR
>> 368 <https://github.com/nhibernate/nhibernate-core/pull/368>) from going
>> into this release? I really don't like it that NHibernate is broken because
>> of me ;-)
>> If anything is missing in that PR, please say so.
>>
>> On Saturday, November 15, 2014 8:49:49 AM UTC+1, Alexander Zaytsev wrote:
>>>
>>> Hi everyone,
>>>
>>> NHibernate 4.0.2 General Availability is now available for download from
>>> Sourceforge and Nuget.
>>>
>>> http://sourceforge.net/projects/nhibernate/?source=directory
>>>
>>> This includes fixes for regressions in NH 4.0.1, and some fixes for
>>> mapping-by-code and Firebird issues.
>>> Please see the full release notes for more information:
>>> https://github.com/nhibernate/nhibernate-core/blob/4.0.2.GA/
>>> releasenotes.txt
>>>
>>> Full list of changes:
>>> [4.0.1.GA] https://nhibernate.jira.com/issues/?jql=project%
>>> 20%3D%20NH%20AND%20resolution%20%3D%20Fixed%20AND%
>>> 20fixVersion%20%3D%204.0.2
>>>
>>> Best Regards,
>>> Alexander
>>>
>>  --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nhibernate-development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"nhibernate-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to