Menu
▾
▴
springframework-developer
|
From: <jue...@we...> - 2004-12-08 18:07:51
|
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. =20 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. =20 Thoughts? =20 Juergen =20 ________________________________ 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 |
|
From: <jue...@we...> - 2004-12-08 22:24:54
|
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 |
|
From: Colin S. <col...@ex...> - 2004-12-08 22:31:17
|
I'll see. All this does is add implementations for the two template methods in the class, and the ejbtest sample does use those methods already, and runs in JBoss. So it is not a big deal to test. Until today, I didn't know we were really planning 1.1.4, so I guess it's not as important to get this in there now, if 1.1.4 is still coming. jürgen höller [werk3AT] wrote: >Colin, > >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. > >Juergen > > >________________________________ > >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ürgen höller [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ürgen höller [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 >> >> >> >> > > > >------------------------------------------------------- >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 > > |
|
From: <jue...@we...> - 2004-12-08 23:02:26
|
Well, we absolutely need to release 1.1.3 this week, JDK 1.3 = compatibility being the main reason. And it looks like there's enough = minor stuff left (and new reports expected for the coming weeks) to = justify 1.1.4... We can still decide against it, but on the other hand = 1.2 final is still a while away. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Colin Sampaleanu Gesendet: Mi 08.12.2004 23:30 An: spr...@li... Betreff: Re: [Springframework-developer] Preparing for 1.1.3 I'll see. All this does is add implementations for the two template methods in the class, and the ejbtest sample does use those methods already, and runs in JBoss. So it is not a big deal to test. Until today, I didn't know we were really planning 1.1.4, so I guess it's not as important to get this in there now, if 1.1.4 is still = coming. j=FCrgen h=F6ller [werk3AT] wrote: >Colin, > >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. > >Juergen > > >________________________________ > >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. >=20 > >>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 > > > > >------------------------------------------------------- >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 |
|
From: Colin S. <col...@ex...> - 2004-12-08 23:12:31
|
The other thing that I need to find 10 min for is to document the import element. That's probably the most important of the outstanding documentation tasks. jürgen höller [werk3AT] wrote: >Well, we absolutely need to release 1.1.3 this week, JDK 1.3 compatibility being the main reason. And it looks like there's enough minor stuff left (and new reports expected for the coming weeks) to justify 1.1.4... We can still decide against it, but on the other hand 1.2 final is still a while away. > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag von Colin Sampaleanu >Gesendet: Mi 08.12.2004 23:30 >An: spr...@li... >Betreff: Re: [Springframework-developer] Preparing for 1.1.3 > > > >I'll see. All this does is add implementations for the two template >methods in the class, and the ejbtest sample does use those methods >already, and runs in JBoss. So it is not a big deal to test. > >Until today, I didn't know we were really planning 1.1.4, so I guess >it's not as important to get this in there now, if 1.1.4 is still coming. > > >jürgen höller [werk3AT] wrote: > > > >>Colin, >> >>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. >> >>Juergen >> >> >>________________________________ >> >>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ürgen höller [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ürgen höller [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 >>> >>> >>> >>> >>> >>> >> >>------------------------------------------------------- >>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 >> >> >> >> > > > >------------------------------------------------------- >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 > > |
|
From: <jue...@we...> - 2004-12-10 19:40:46
|
Everybody, =20 I plan to - finally! - release 1.1.3 tomorrow, with a couple of = last-minute issues addressed. That's a hard deadline, as I'll leave for = Belgium (JavaPolis) on Sunday. =20 Juergen =20 ________________________________ Von: spr...@li... im Auftrag = von Colin Sampaleanu Gesendet: Do 09.12.2004 00:12 An: spr...@li... Betreff: Re: [Springframework-developer] Preparing for 1.1.3 The other thing that I need to find 10 min for is to document the import element. That's probably the most important of the outstanding documentation tasks. j=FCrgen h=F6ller [werk3AT] wrote: >Well, we absolutely need to release 1.1.3 this week, JDK 1.3 = compatibility being the main reason. And it looks like there's enough = minor stuff left (and new reports expected for the coming weeks) to = justify 1.1.4... We can still decide against it, but on the other hand = 1.2 final is still a while away. > >Juergen > > >________________________________ > >Von: spr...@li... im Auftrag = von Colin Sampaleanu >Gesendet: Mi 08.12.2004 23:30 >An: spr...@li... >Betreff: Re: [Springframework-developer] Preparing for 1.1.3 > > > >I'll see. All this does is add implementations for the two template >methods in the class, and the ejbtest sample does use those methods >already, and runs in JBoss. So it is not a big deal to test. > >Until today, I didn't know we were really planning 1.1.4, so I guess >it's not as important to get this in there now, if 1.1.4 is still = coming. > > >j=FCrgen h=F6ller [werk3AT] wrote: > >=20 > >>Colin, >> >>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. >> >>Juergen >> >> >>________________________________ >> >>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. >> >> >> =20 >> >>>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 >>> >>> =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 >> >> >> >> >>------------------------------------------------------- >>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 > > > > >------------------------------------------------------- >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 |
|
From: Dmitriy K. <dko...@ru...> - 2004-12-08 18:16:56
|
The schedule looks good to me. Dmitriy. 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 t= hey can be solved immediately. I'd like to do the actual release tomo= rrow. >=20 >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 wil= l be 1.2 RC1 then - end of January or early February. >=20 >Thoughts? >=20 >Juergen >=20 > >________________________________ > >Von: spr...@li... im Auftra= g 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 wh= ether 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 incompatibilitie= s that slipped into 1.1.2 is an important factor here, but also getti= ng 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 a= lso be fixed tomorrow or on Tuesday, of course. > >There are also a couple of documentation issues in JIRA. They are no= t critical for 1.1.3, but it would be good to address them as early a= s possible. > >Juergen > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real us= ers. >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-develop= er > > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real us= ers. >Discover which products truly live up to the hype. Start reading now= .=20 >http://productguide.itmanagersjournal.com/ >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-develop= er > =20 > |
|
From: Rob H. <ro...@ca...> - 2004-12-08 18:33:34
|
I added a few fixes for problems today, but I don't think I'll get anything else done in time. We still need to decide on a solution to the CGLIB/no arg constructor problem since I really want to get that fix in for 1.1.4. Rob jürgen höller [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ürgen höller [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 > > > > |
|
From: Rob B. <cro...@ya...> - 2004-12-08 19:44:50
|
jürgen, Please take a look at: http://article.gmane.org/gmane.comp.java.springframework.user/4708 I think it would be a useful addition, and if this could get out in 1.1.3 that would really help me. Thanks Rob --- jürgen höller [werk3AT] <jue...@we...> 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ürgen höller [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 > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Colin S. <col...@ex...> - 2004-12-08 20:17:17
|
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ürgen höller [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ürgen höller [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 > > |
