Going to throw another perhaps crazy suggestion out there... Thinking we should consider: 1) branching 4.1 2) integrating my JPA 2.1 work onto master 3) merge master (with JPA 2.1) to metamodel branch
Couple of thought processes go into this. First, I do not see us doing anymore 4.x releases outside of possibly doing a 4.2 *specifically* to release JPA 2.1 support. Ideally I want JPA 2.1 support to be released as 5.0 hand-in-hand with the metamodel work. The only reason we would not go that route is if the metamodel work drags on and threatens us releasing JPA 2.1 support in a timely manner. I do not see that happening, just stating a known condition. Besides the JPA 2.1 support is actually up-to-date with the latest available specs (and actually a little bit ahead of the latest available spec draft after this week). So again, all-in-all I still do not foresee the need for a 4.2 at this time. On 07/15/2012 08:27 AM, Strong Liu wrote: > Hi there, > > I think we should do this again since there are some changes in master that I > want to use in metamodel, and maybe we should do this regularly to minimize > the conflicts? > > Steve is the best to do this, since he already did this once, but in case he > is busying on other stuff, I'm voluntarily to do this . > > WDYT? > > > > > ------------------------- > Best Regards, > > Strong Liu <stliu at hibernate.org> > http://about.me/stliu/bio > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev -- st...@hibernate.org http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
