Re: [Springframework-developer] Preparing for 1.1.3

[<jue...@we...>]

Colin,
=20
I wouldn't mind deferring this to 1.1.4, in particular if there's not =
enough time to test the final implementation in a target environment. So =
if it doesn't get completely ready till tomorrow, please commit it after =
the actual 1.1.3 release.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Colin Sampaleanu
Gesendet: Mi 08.12.2004 21:17
An: spr...@li...
Betreff: Re: [Springframework-developer] Preparing for 1.1.3



I think tonight I should do SPR-358:
  http://opensource.atlassian.com/projects/spring/browse/SPR-358
there's been no more discussion on it. It's essentially zero risk, since
it just moves existing working code used in the ejbtest integration test
sample, into ContextLoader...

Colin


j=FCrgen h=F6ller [werk3AT] wrote:

>From my side, we're ready for the 1.1.3 release. All issues in JIRA =
that are still marked for 1.1.3 should be deferred to 1.1.4, unless they =
can be solved immediately. I'd like to do the actual release tomorrow.
>
>It seems that a 1.1.4 release will be necessary to get all sorts of =
minor things in; probably in early January. Next stop after 1.1.4 will =
be 1.2 RC1 then - end of January or early February.
>
>Thoughts?
>
>Juergen
>
>
>________________________________
>
>Von: spr...@li... im Auftrag =
von j=FCrgen h=F6ller [werk3AT]
>Gesendet: Mo 06.12.2004 01:19
>An: spr...@li...
>Betreff: [Springframework-developer] Preparing for 1.1.3
>
>
>
>Hi everybody,
>
>I've committed a bunch of stuff for 1.1.3, mainly addressing recent =
JIRA issues but also refining HTTP invoker internals etc. Anyone who has =
some time left, please give a current snapshot a try and check whether =
everything works for you!
>
>I'd like to do the actual 1.1.3 release as early as this Wednesday, =
unless there are major obstacles. Fixing the JDK 1.3 incompatibilities =
that slipped into 1.1.2 is an important factor here, but also getting a =
couple of other things out early.
>
>This means that remaining issues that are not of critical importance =
should be deferred, either till 1.2 RC1 or till 1.1.4 (the need for such =
a further 1.1.x point needs to be discussed). Minor issues can also be =
fixed tomorrow or on Tuesday, of course.
>
>There are also a couple of documentation issues in JIRA. They are not =
critical for 1.1.3, but it would be good to address them as early as =
possible.
>
>Juergen
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real =
users.
>Discover which products truly live up to the hype. Start reading now.
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real =
users.
>Discover which products truly live up to the hype. Start reading now.
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer