Hi Don, I think we're close. I had wanted to get artifacts up to vote on this week. I guess the open jpa release vote closes 2am GMT Saturday and those fixes for Aries JPA issues are OPENJPA-1491 and OPENJPA-1524 right? There are workaround for both the 1491 workaround is in Aries itself so that wouldn't affect users, the workaround for 1524 mentioned by Joe is a change to a blueprint.xml so impacts users.
Ideally I'd like to pull in beta3. Anyone else have a preference? Cheers, Jeremy There I think it's worth waiting that little bit extra for it so the 1524 workaround isn't needed On 24 March 2010 02:39, Donald Woods <[email protected]> wrote: > What's the status on a release? I've just put a openjpa-2.0.0-beta3 up > for a vote, which includes fixes for two Aries JPA issues.... > > > -Donald > > > On 1/26/10 12:34 PM, Jeremy Hughes wrote: >> There's been a lot of activity lately so I'd like to propose we do a >> release so we can get some wider user feedback. I think we should give >> it a version of 0.1 and stick to versions <1 while we're in the >> Incubator. >> >> Then there is the question of whether to independently version the >> high level modules or keep them lock-step. For now I think we should >> keep them lock-step until we feel a need to change that. >> >> What does everyone think? >> >> Thanks, >> Jeremy >> >
