It's building now. I ran into weird issues with the release plugin last night but I think I've ironed those out.
Should have a release candidate tonight / tomorrow. -mike On Wed, Mar 4, 2009 at 12:39 PM, Joe Bohn <[email protected]> wrote: > Hi Mike, > > How are things looking for the 1.2.1 release? Do you anticipate having a > release candidate soon? > > Thanks, > Joe > > > > Michael Dick wrote: > >> Sure, I'll start on it later this afternoon / tonight. >> >> -mike >> >> On Mon, Mar 2, 2009 at 9:42 AM, Donald Woods <[email protected]> wrote: >> >> Everything is a go from the Geronimo side, as we got a clean TCK run >>> completed. Can we start a OpenJPA 1.2.1 release now? >>> >>> >>> Thanks, >>> -Donald >>> >>> >>> >>> Donald Woods wrote: >>> >>> Mike, it looks like all of our TCK failures related to JPA have been >>>> fixed >>>> and verified. Can you start the process of cutting a 1.2.1 branch >>>> while we >>>> finish our TCK runs? I'd still wait until we have the complete results >>>> in >>>> (probably sometime Friday) before you start a RC vote. >>>> >>>> Thanks, >>>> Donald >>>> >>>> >>>> Michael Dick wrote: >>>> >>>> Hi Kevan, >>>>> >>>>> I've been planning on doing a 1.2.1 release "real soon now" for a >>>>> while. >>>>> I'll start working on it later this week (early next week at the >>>>> latest). >>>>> >>>>> Regards, >>>>> >>>>> -mike >>>>> >>>>> On Tue, Jan 27, 2009 at 11:04 AM, Kevan Miller <[email protected] >>>>> >>>>>> wrote: >>>>>> >>>>> Thanks Kevin and Jeremy for helping to resolve OPENJPA-872. >>>>> >>>>>> Is there an outlook for an OpenJPA 1.2.1 release? Geronimo is going to >>>>>> need >>>>>> a release prior to releasing Geronimo 2.1.4 and 2.2. I guess we could >>>>>> consider using openjpa.jdbc.QuerySQLCache=false as a work-around, but >>>>>> I'd >>>>>> rather avoid that... Meantime, we'll start using 1.2.1-SNAPSHOT >>>>>> >>>>>> --kevan >>>>>> >>>>>> >>>>> >> >
