+1 to Jeremy's comments and to the release. I haven't seen anything that warrants a re-spin, nice job Donald!
-mike On Tue, Jan 26, 2010 at 1:11 PM, Jeremy Bauer <[email protected]> wrote: > [X] +1 > [ ] 0 > [ ] -1 (and reason why) > > IMO, let's spend the time putting together the release announce page and > news item. Additional items/issues/whatever can be doc'd there if we > choose > to do so. The feature list can also be polished for the announce. Check > out the announce page for M3[1]. I'm assuming we'll do something similar > for the beta. > > -Jeremy > > [1] http://openjpa.apache.org/openjpa-200-milestone-3.html > > On Tue, Jan 26, 2010 at 1:00 PM, Kevin Sutter <[email protected]> wrote: > > > I agree with the sentiment that an undocumented feature really doesn't > > exist. I use this reasoning all the time. But, to force a respin of the > > Beta driver to document this osgi module seems like overkill. The worse > > thing that happens is that people don't know it exists. We can resolve > > that > > with documentation in trunk and forum postings. > > > > Kevin > > > > On Tue, Jan 26, 2010 at 12:27 PM, Pinaki Poddar <[email protected]> > > wrote: > > > > > > > > > Thanks for the comments, but I don't think any of the below requires > a > > > > new release candidate, given this is a Beta release :-) > > > > > > My only concern about openjpa-osgi module being added without a single > > > mention. While OSGi-enablement of OpenJPA is a great addition (thanks > to > > > you), without any mention of such an important new feature does not do > > > justice to the work. > > > > > > Of course, there are certain liberties with a Beta release. But adding > a > > > module without any mention does not fall into that category. > > > > > > ----- > > > Pinaki > > > -- > > > View this message in context: > > > > > > http://n2.nabble.com/VOTE-OpenJPA-2-0-0-beta-release-candidate-2-tp4458924p4462374.html > > > Sent from the OpenJPA Developers mailing list archive at Nabble.com. > > > > > >
