Re: [Springframework-developer] Final preparations for 1.0.1

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

If we're going to need 1.0.2 anyway, I'd say release 1.0.1 tonight.
Otherwise, I would like to commit my CGLIB fix right away so we have a we=
ek
to test it in the wild before a 1.0.1 release next week.

Ideally I'd feel more comfortable if we weren't changing things (even min=
or
stuff) so close to the release date. I'm keen on a code freeze of at leas=
t a
few days before each maintenance release.

Regards,
Rod

----- Original Message -----
From: "j=FCrgen h=F6ller [werk3AT]" <jue...@we...>
To: <spr...@li...>
Sent: Tuesday, April 20, 2004 10:57 PM
Subject: [Springframework-developer] Final preparations for 1.0.1


Everybody,

I've just committed the name change in the AOP package that we've discuss=
ed
a while ago, namely AbstractPrototypeTargetSource ->
AbstractPrototypeBasedTargetSource.

There's still two further minor enhancements that I'd like to look at, so
the question is how urgent 1.0.1 actually is. We've got two options: eith=
er
release 1.0.1 tomorrow evening, with everything that's in CVS by then, or
release it early next week, with those further issues addressed too. Of
course, new issues might get reported in the meantime again, so I'm somew=
hat
inclined to still release 1.0.1 tomorrow, and do a 1.0.2 release in a cou=
ple
of weeks.

I'd like to clarify the JdbcUtils.extractDatabaseMetaData issue in any ca=
se
for 1.0.1, as we need to get that released API right.

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