|
From: Colin S. <col...@ex...> - 2004-04-02 21:43:01
|
+0 I agree for the most part with trying to catch other issues, however the=20 Hibernate session bug is _very_ nasty for people that actually get hit=20 by it. Now those people can pull out and run a CVS if they think to come=20 here and ask, but still... Rod Johnson wrote: >I suggest that we sit on this code for at least a week until we release = it, >so we can catch anything else. How about we target Monday week for relea= se? > >A 1.0.1 release should be driven by stability, not date, so we should se= e if >any more issues come out of the woodwork. > >----- Original Message ----- >From: "j=FCrgen h=F6ller [werk3AT]" <jue...@we...> >To: <spr...@li...> >Sent: Friday, April 02, 2004 10:57 AM >Subject: [Springframework-developer] Preparing for 1.0.1 > > >Hi everybody, > >From my point of view, the code is ready for release 1.0.1. There were a >couple of bug fixes and minor enhancements since 1.0 final. The most >important fix is proper Hibernate/JTA resource management when flush fai= ls. >Enhancements include the introduction of the MessageCodesResolver interf= ace >in the validation package, and a more efficient internal implementation = of >AbstractMessageSource. See the changelog for details. > >Please give the current CVS snapshot a try. There shouldn't be any issue= s, >as changes are minor and just affect specific functionality. I'd like to >target mid next week for the release, i.e. two weeks after 1.0 final. In= the >meantime, the only thing I plan to address is the lack of remoting cover= age >in the reference docs. If anyone feels the need to improve other parts o= f >the docs, please do so till mid next week! > >Juergen > =20 > |