Menu
▾
▴
springframework-developer
|
From: <jue...@we...> - 2004-04-02 10:00:01
|
Hi everybody, =20 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 = fails. Enhancements include the introduction of the MessageCodesResolver = interface in the validation package, and a more efficient internal = implementation of AbstractMessageSource. See the changelog for details. =20 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 coverage in the reference docs. If anyone feels the need to = improve other parts of the docs, please do so till mid next week! =20 Juergen |
|
From: Colin S. <col...@ex...> - 2004-04-02 14:26:33
|
I've been using the CVS version without issues. I did some=20 proofing/rewriting in the beans chapter earlier this week/last week, and=20 should probably be able to find time to do the rest by the time you cut=20 the release. j=FCrgen h=F6ller [werk3AT] wrote: >Hi everybody, >=20 >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 imp= ortant fix is proper Hibernate/JTA resource management when flush fails. = Enhancements include the introduction of the MessageCodesResolver interfa= ce in the validation package, and a more efficient internal implementatio= n of AbstractMessageSource. See the changelog for details. >=20 >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= coverage in the reference docs. If anyone feels the need to improve othe= r parts of the docs, please do so till mid next week! >=20 >Juergen > =20 > |
|
From: <tho...@tr...> - 2004-04-02 16:28:31
|
I noticed a lot of changes in CVS yesterday - any area in particular where we should look out for problems? My database product name caching fix is in CVS now - so even if you don't preconfigure a JdbcTemlpate, you should now only see one metadata lookup and the rest should be 'found in cache' entries in the log (INFO). Thomas Quoting Colin Sampaleanu <col...@ex...>: > I've been using the CVS version without issues. I did some=20 > proofing/rewriting in the beans chapter earlier this week/last week, and=20 > should probably be able to find time to do the rest by the time you cut=20 > the release. > > j=FCrgen h=F6ller [werk3AT] wrote: > > >Hi everybody, > >=20 > >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 imp= > ortant fix is proper Hibernate/JTA resource management when flush fails. = > Enhancements include the introduction of the MessageCodesResolver interfa= > ce in the validation package, and a more efficient internal implementatio= > n of AbstractMessageSource. See the changelog for details. > >=20 > >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= > coverage in the reference docs. If anyone feels the need to improve othe= > r parts of the docs, please do so till mid next week! > >=20 > >Juergen > > =20 > > > > > > ------------------------------------------------------- > 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_id=3638&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Rod J. <rod...@in...> - 2004-04-02 21:23:55
|
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 |
|
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 > |
|
From: Alef A. <al...@jt...> - 2004-04-03 12:37:49
|
I tend to be in favor of waiting a little while. Tiny issues keep coming = up and I guess it's worth waiting for some more. As Rod says, stability is = key, no need to rush here... In the meantime I think we should inform users of major issues (like the Hibernate one) in a more prominent way however, along with some = potential workarounds... Alef > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On = Behalf > Of Colin Sampaleanu > Sent: Friday, April 02, 2004 11:43 PM > To: spr...@li... > Subject: Re: [Springframework-developer] Preparing for 1.0.1 >=20 > +0 >=20 > I agree for the most part with trying to catch other issues, however = the > Hibernate session bug is _very_ nasty for people that actually get hit > by it. Now those people can pull out and run a CVS if they think to = come > here and ask, but still... >=20 > Rod Johnson wrote: >=20 > >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 > release? > > > >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 > fails. > >Enhancements include the introduction of the MessageCodesResolver > interface > >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 > 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 > coverage > >in the reference docs. If anyone feels the need to improve other = parts of > >the docs, please do so till mid next week! > > > >Juergen > > > > >=20 >=20 >=20 > ------------------------------------------------------- > 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 |
