That's perfectly fine for me.
I gonna kick out the 2.2.x branch and move trunk back to 2.2.0-SNAPSHOT. I just had the impression that asking 3 times if the branch is ok was fine ;) LieGrue, strub >________________________________ > From: Albert Lee <[email protected]> >To: [email protected]; Mark Struberg <[email protected]> >Sent: Wednesday, January 11, 2012 6:17 PM >Subject: Re: [DISCUSS] release openjpa-2.2.0? > > >Mark, > >Usually we announce the time frame the release will be cut so that people can >finish the work in progress before the release time. At the mean time, any >outstanding JIRA issues need to be marked accordingly (resolved, closed etc) >per the release doc >(http://openjpa.apache.org/apache-nexus-release-process-12x-21x.html) in >preparation of the release notes. Per Donald's suggestion, TCK verification >should be completed to make sure we are in good standing. > >If you don't mind, it would be good to revert the release branched, give dev >folks time to fix any outstanding issues and make sure trunk is stabilized >before cutting the new 2.2.x branch. > >Thanks, >Albert Lee. > > >On Wed, Jan 11, 2012 at 4:43 AM, Mark Struberg <[email protected]> wrote: > >Hi Pinaki! >> >>I already created the 2.2.x branch a day before you sent this message, but >>will delete it again if you think it' worth the troubles. >> >>The other option is to just cherry-pick your changes and apply them to 2.2.x >>as well. >> >> >>I'm also currently investigating an error I have locally with ManagedCache >>dup-load (line 123) containing an id which I have no idea why it is already >>stored. Might be a user error though. Do you know if something got changed in >>this area the last few months? >> >>LIeGrue, >> >>strub >> >> >> >>----- Original Message ----- >> >>> From: Pinaki Poddar <[email protected]> >>> To: [email protected] >>> Cc: >>> Sent: Tuesday, January 10, 2012 7:13 PM >>> Subject: Re: [DISCUSS] release openjpa-2.2.0? >>> >> >>> I suggest that we hold this branch cutting for few more days as trunk >>> contains some in-flight commits related to OPENJPA-2099. These commits >>> (related to rebinding select parameters) are not unclean or defective, but >>> they are incomplete as a part of a transaction. Given that select reuse >>> related work of OPENJPA-2099 addresses some basic constructs of OpenJPA, the >>> codebase will be consistent when the work reaches a stable (or at least >>> meta-stable) state which could be as early as Jan 11 17:00 hrs Pacific >>> Standard Time. >>> >>> ----- >>> Pinaki Poddar >>> Chair, Apache OpenJPA Project >>> -- >>> View this message in context: >>> http://openjpa.208410.n2.nabble.com/DISCUSS-release-openjpa-2-2-0-tp7151227p7173084.html >>> Sent from the OpenJPA Developers mailing list archive at Nabble.com. >>> >> > > >-- >Albert Lee. > > >
