To not let this slip.
What are the release plans in general? Do you like to start with the work on the new JPA spec soon (guess this might take another year to get finished). I'd rather keep the trunk as main development stage and would like to work towards a 2.2.1 afterwards on trunk. The reason why I ask this is for the branch we like to create. It's a difference if we just create a '2.2.0-mt' branch (mt for maintenance) only for getting 2.2.0 out of the door, and continue our main development effort on trunk. Or if we create a '2.2.x' branch and do the most work there (and need to merge all work over to trunk). I'm +1 for 2.2.0-mt If noone objects then I like to start this new branch middle of next week. What work needs to be done until then? My gut feeling says: * review open JIRAs * verify and resolve the ones already fixed * update the fix-version to 2.2.1 for the others * run the TCK * verify/update the documentation of new features. This reminds me that our pdf doesn't contain good information for the new openjpa-maven-plugin. I was also not able to find where we deploy the plugin documentation to. This is imo something we should review/fix before we branch. feel free to add missing tasks. LieGrue, strub ----- Original Message ----- > From: Mark Struberg <[email protected]> > To: "[email protected]" <[email protected]> > Cc: > Sent: Wednesday, January 4, 2012 8:11 PM > Subject: Re: [DISCUSS] release openjpa-2.2.0? > > I'd just branch the trunk and remove JEST later. Or just keep it and mark it > as 'experimental' - doesn't hurt! > > LieGrue, > strub > > > > ----- Original Message ----- >> From: Kevin Sutter <[email protected]> >> To: [email protected]; Donald Woods <[email protected]> >> Cc: >> Sent: Wednesday, January 4, 2012 7:41 PM >> Subject: Re: [DISCUSS] release openjpa-2.2.0? >> >> Donald, >> >>> I would suggest someone verifying a clean TCK run before we branch. >>> >> >> Excellent idea. We used to have someone from the Apache community do this >> for us since not everybody has access to the TCK. Is there someone that >> can step up to do this? >> >> >>> >>> Also, are there any samples or experimental code that needs to be > removed >>> or cleaned up before we create a 2.2.0 release? >>> >> >> Since you brought this up... I'm think we need to re-think the JEST > module >> that is currently in trunk. Pinaki originally put it into trunk with the >> hopes of solidifying it before we do another release. I don't think > that >> effort has transpired. Since it's a separate module, maybe it can be >> pulled before creating the 2.2.0 release and 2.2.x service stream and then >> put back into trunk? Other ideas? >> >> Kevin >> >> >>> >>> -Donald >>> >>> >>> >>> ________________________________ >>> From: Mark Struberg <[email protected]> >>> To: openjpa-dev <[email protected]> >>> Cc: David Blevins <[email protected]> >>> Sent: Wednesday, January 4, 2012 12:11 PM >>> Subject: [DISCUSS] release openjpa-2.2.0? >>> >>> Hi folks! >>> >>> I've now used openjpa-2.2.0 excessively and it looks very good to > me. >>> What do you think about going forward and shipping a 2.2.0? >>> Or at least a RC1... >>> >>> OpenEJB and Geronimo are waiting for an openjpa-2.2.x release as well > ;) >>> >>> LieGrue, >>> strub >>> >> >
