Re: [Springframework-developer] Preparing for 1.0.1

[Rod J. <rod...@in...>]

I suggest that we sit on this code for at least a week until we release i=
t,
so we can catch anything else. How about we target Monday week for releas=
e?

A 1.0.1 release should be driven by stability, not date, so we should see=
 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 fail=
s.
Enhancements include the introduction of the MessageCodesResolver interfa=
ce
in the validation package, and a more efficient internal implementation o=
f
AbstractMessageSource. See the changelog for details.

Please give the current CVS snapshot a try. There shouldn't be any issues=
,
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 covera=
ge
in the reference docs. If anyone feels the need to improve other parts of
the docs, please do so till mid next week!

Juergen


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer