I've merged a few of these pull requests - those that looked tiny and had a
theoretically breaking API change. Now it's time for release.


2014-08-14 2:27 GMT+02:00 Ricardo Peres <[email protected]>:

> Hi,
>
> I'm the responsible for quite a few... unfortunately, I screwed up
> somewhere, and some of the pull requests got mixed up... arrgghh...
> I think Alex is having a bad time looking at it! :-(
> Will try to sort that out tomorrow. In the meantime, I think NH-3110
> <https://nhibernate.jira.com/browse/NH-3110>, NH-3658
> <https://nhibernate.jira.com/browse/NH-3658>, NH-3404
> <https://nhibernate.jira.com/browse/NH-3404> and NH-3402
> <https://nhibernate.jira.com/browse/NH-3402> are safe.
>
> RP
>
>
> On Wednesday, August 13, 2014 10:22:06 PM UTC+1, Oskar Berggren wrote:
>>
>> Hi,
>>
>> Lots of new shiny pull requests today! And I was so happy to be back
>> below 50 open requests the other week. Haha... :)
>>
>> Anyway in my opinion we should hold off on further merges to 3.4.x and
>> master until we have the releases done. Exceptions being regressions and
>> one or two of the issues already planned for GA in JIRA.
>>
>> Maybe, just maybe, we might have releases this weekend.
>>
>> If there are any non-regressions bugs or feature limitations for which a
>> fix is _available_ AND that involves breaking changes I might entertain a
>> discussion about it. Otherwise I would prefer to have it wait for a minor
>> release some weeks after GA.
>>
>>
>> /Oskar
>>
>>  --
>
> ---
> 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