Hi, I have the following outstanding issues:
http://216.121.112.228/browse/NH-2092 <http://216.121.112.228/browse/NH-2092>http://216.121.112.228/browse/NH-2093 <http://216.121.112.228/browse/NH-2093>http://216.121.112.228/browse/NH-2094 <http://216.121.112.228/browse/NH-2094>http://216.121.112.228/browse/NH-2102 <http://216.121.112.228/browse/NH-2102>2 of the have patches. I had to turn off field intercepting proxies (new feature by ayende a while ago) by patching the castle proxy generator in order to use the latest trunk. Regards, Johannes On Fri, Jul 16, 2010 at 8:49 AM, Torkel Ödegaard <[email protected]>wrote: > > Please also review http://216.121.112.228/browse/NH-2061 > > On Jul 14, 6:08 pm, Fabio Maulo <[email protected]> wrote: > > You can do anything allowed by your account permission excluding break > > existing tests. > > > > P.S. Now I got go, send me a private mail with the info of your JIRA > > account. > > > > On Wed, Jul 14, 2010 at 12:29 PM, Julian <[email protected]> > wrote: > > > I noticed that there are uncommitted patches (with tests) on Jira - > > > including some of my own - and I'm wondering if anybody has any > > > objection to me commiting them to the trunk. > > > > > For example: > > >http://216.121.112.228/browse/NH-2111 > > >http://216.121.112.228/browse/NH-2069 > > > > > Does the upcoming 3.0.0-Alpha1 release impose some limitations on what > > > should be committed? > > > > > (Also, I do not have permission to close Jira issues once I have > > > commited them) > > > > -- > > Fabio Maulo >
