On Mar 2, 2011, at 5:06 AM, Jean-Louis MONTEIRO wrote: > Finally, i'm not in favour of merging JPA 2 changes in 3.1.x branch. > > I would prefer to keep our 3.1.x branch Java EE 5 compatible. > So instead of merging JPA 2 to 3.1.x branch,
Same here. What if we just called that new codebase 3.2 and then trunk maybe 4.0. > I would prefer to push a 3.2-alpha1 just after JPA 2 support and before > refactoring. That was my initial thought as well, but then I thought about all the work we've done on 3.2 that merged into 3.1.x. I count 180 commits and 58 merges. It was only after that that I thought about just starting from 3.1.x and merging the one feature in. -David
