I am ready to start working on changes for 3.6. That means I need to
branch off 3.5 work. Anyone not ready for that (obviously once svn is
accessible again)?
--
Steve Ebersole
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.j
Hi,
I created http://opensource.atlassian.com/projects/hibernate/browse/HV-310for
that.
Gunnar
2010/4/19 Emmanuel Bernard
>
> On 18 avr. 2010, at 20:57, Gunnar Morling wrote:
>
> >
> > WDYT? If we come to the conclusion that for instance
> ResourceBundleMessageInterpolator should be moved to a
First meeting. Went well.
1) We discussed our experiences with time-boxing in the 3.5 releases.
Generally positive. Some felt 2 weeks may have been a bit too often.
We will play with time moving forward to find the best balance which may
be an alternation: slow (alphas), fast (betas and crs),
They upgraded it to 4.1 (from 4.0) as part of the process yes.
On Mon, 2010-04-19 at 21:19 +0800, Strong Liu wrote:
> JIRA version changed/updated?
>
> or only me?
>
> -
> Best Regards,
>
> Strong Liu
>
> On Apr 18, 2010, at 11:43 PM, Steve Ebersole wrote:
>
> > FYI..
Hi Chris,
Your option 3 does sound interesting all right.
If putting a link on Hibernate.org could still be done and because we do
have control of including the Dialect with the solidDB JDBC driver, this
approach sounds like it would suit both yourselves and us. Also we would
be responsible for r
On 04/17/2010 08:29 PM, Strong Liu wrote:
> 5. for hudson job, we need it builds hibernate trunk code on jdk1.5 and run
> the tests both on jdk1.5 and jdk6.
> Juca, you will help me on this, right? :D
Sure thing. I did a test job last week, which tested the execution of
the test suite on both J
Hi Steve,
Thanks for explaining the issues here. Our current Hibernate code was done
a while back and is in need to some update and ideally some kind of
"approval" from the likes of yourself on this list.
I will have to check about LGPL and signing agreements but in terms of
ownership we can certa
yes, you're right, actually this is the main concern from Steve :)
if we agree to do that, I will find a way to enforce the release must be done
on JDK5.
maybe add some check script to the pom by gmaven
On 2010-4-19, at 下午4:28, Emmanuel Bernard wrote:
> My only fear is that when releasing, some
My only fear is that when releasing, someone (like me) would forget to force
JDK 5. So would that be enforced in the new scheme for releases?
On 17 avr. 2010, at 20:29, Strong Liu wrote:
> Okay, after the discussion with Steve on IRC, here is the update:
>
> 1. lots of intended contributors onl
On 18 avr. 2010, at 20:57, Gunnar Morling wrote:
>
> WDYT? If we come to the conclusion that for instance
> ResourceBundleMessageInterpolator should be moved to another package, I think
> it might be a good idea to do that for 4.1, as right now the number of
> concerned classes still seems ve
Hi,
I am not a OSGi expert, but I guess we can think about this a little more.
As you say org.hibernate.validator and org.hibernate.validator.constraints
should definitely
be public. Regarding the classes in org.hibernate.validator.engine I would
suggest to create a
new package. ResourceBundle
11 matches
Mail list logo
