Menu
▾
▴
springframework-developer
|
From: Juergen H. <ju...@in...> - 2005-09-09 10:35:59
|
Everyone, I'm inclined to do a Spring 1.2.5 release before going for 1.3 RC1: resolving the already known issues in the 1.2.x line, as reported on our JIRA and partly already fixed in CVS (currently with target 1.3 RC1). The 1.2.5 release, if desired, would have to happen end of next week. Afterwards, CVS HEAD would be dedicated to 1.3 development, with a 1.2 maintenance branch alongside. Ideally, the 1.2.5 release would include all minor fixes done since 1.2.4 (there were quite a few, including javadoc fixes). Hence, I would like to create it from CVS HEAD rather than from a 1.2.4 branch. This means that already committed 1.3 features would have to be temporarily moved to the sandbox, unless we decide to release them in 1.2.5 already. The request log filter and named JDBC statement parameters are candidates for 1.2.5, I guess, as they have been planned for 1.2.x initially. Thomas, if you'd like to not release named JDBC statement parameters before 1.3 RC1, I would temporarily move it to the sandbox and back after the actual 1.2.5 release. I'll leave that decision up to you. Regards, Juergen ----- Juergen Hoeller Interface21 - Spring Services from the Source http://www.springframework.com |
|
From: Thomas R. <tho...@tr...> - 2005-09-09 12:19:30
|
Juergen, I'd prefer to keep the named parameters for a 1.3RC1 release - there are still some lose ends and little testing has been done on most of it. Thomas On Sep 9, 2005, at 6:35 AM, Juergen Hoeller wrote: > Everyone, > > I'm inclined to do a Spring 1.2.5 release before going for 1.3 RC1: > resolving the already known issues in the 1.2.x line, as reported > on our > JIRA and partly already fixed in CVS (currently with target 1.3 > RC1). The > 1.2.5 release, if desired, would have to happen end of next week. > Afterwards, CVS HEAD would be dedicated to 1.3 development, with a 1.2 > maintenance branch alongside. > > Ideally, the 1.2.5 release would include all minor fixes done since > 1.2.4 > (there were quite a few, including javadoc fixes). Hence, I would > like to > create it from CVS HEAD rather than from a 1.2.4 branch. This means > that > already committed 1.3 features would have to be temporarily moved > to the > sandbox, unless we decide to release them in 1.2.5 already. > > The request log filter and named JDBC statement parameters are > candidates > for 1.2.5, I guess, as they have been planned for 1.2.x initially. > Thomas, > if you'd like to not release named JDBC statement parameters before > 1.3 RC1, > I would temporarily move it to the sandbox and back after the > actual 1.2.5 > release. I'll leave that decision up to you. > > Regards, > > Juergen > > ----- > Juergen Hoeller > Interface21 - Spring Services from the Source > http://www.springframework.com > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * > Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/ > bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > |
|
From: Juergen H. <ju...@in...> - 2005-09-09 21:26:42
|
Thomas, Do you have the chance to move those classes to the sandbox, potentially holding the JdbcTemplate extensions in a special JdbcTemplate subclass for the time being? I can do that move as well, of course, but I don't want to infer with any local changes you might already have made but not committed yet. In general, we should have clarified the role of CVS HEAD. We need definitive announcements once HEAD turns to the next major release. Currently it still serves as basis for 1.2.5, which will then lead to a 1.2.x maintenance branch (for potential future patches), with CVS HEAD becoming the basis for 1.3. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Thomas Risberg Sent: Friday, September 09, 2005 2:20 PM To: spr...@li... Subject: Re: [Springframework-developer] 1.2.5 release Juergen, I'd prefer to keep the named parameters for a 1.3RC1 release - there are still some lose ends and little testing has been done on most of it. Thomas On Sep 9, 2005, at 6:35 AM, Juergen Hoeller wrote: > Everyone, > > I'm inclined to do a Spring 1.2.5 release before going for 1.3 RC1: > resolving the already known issues in the 1.2.x line, as reported on > our JIRA and partly already fixed in CVS (currently with target 1.3 > RC1). The > 1.2.5 release, if desired, would have to happen end of next week. > Afterwards, CVS HEAD would be dedicated to 1.3 development, with a 1.2 > maintenance branch alongside. > > Ideally, the 1.2.5 release would include all minor fixes done since > 1.2.4 > (there were quite a few, including javadoc fixes). Hence, I would like > to create it from CVS HEAD rather than from a 1.2.4 branch. This means > that already committed 1.3 features would have to be temporarily moved > to the sandbox, unless we decide to release them in 1.2.5 already. > > The request log filter and named JDBC statement parameters are > candidates for 1.2.5, I guess, as they have been planned for 1.2.x > initially. > Thomas, > if you'd like to not release named JDBC statement parameters before > 1.3 RC1, > I would temporarily move it to the sandbox and back after the actual > 1.2.5 release. I'll leave that decision up to you. > > Regards, > > Juergen > > ----- > Juergen Hoeller > Interface21 - Spring Services from the Source > http://www.springframework.com > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices Agile & Plan-Driven Development * Managing Projects & Teams > * Testing & QA Security * Process Improvement & Measurement * > http://www.sqe.com/ bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Thomas R. <tho...@tr...> - 2005-09-09 22:20:25
|
I'll move it over to the sandbox the next couple of days. 1.2.5 wasn't on the roadmap earlier so I went ahead with 1.3 features - I changed the version to 1.3-dev - we should change that to 1.2.5 so the downloadable nightly snapshots are named accordingly. Thomas On Sep 9, 2005, at 5:26 PM, Juergen Hoeller wrote: > Thomas, > > Do you have the chance to move those classes to the sandbox, > potentially > holding the JdbcTemplate extensions in a special JdbcTemplate > subclass for > the time being? I can do that move as well, of course, but I don't > want to > infer with any local changes you might already have made but not > committed > yet. > > In general, we should have clarified the role of CVS HEAD. We need > definitive announcements once HEAD turns to the next major release. > Currently it still serves as basis for 1.2.5, which will then lead > to a > 1.2.x maintenance branch (for potential future patches), with CVS HEAD > becoming the basis for 1.3. > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On > Behalf Of > Thomas Risberg > Sent: Friday, September 09, 2005 2:20 PM > To: spr...@li... > Subject: Re: [Springframework-developer] 1.2.5 release > > Juergen, > > I'd prefer to keep the named parameters for a 1.3RC1 release - > there are > still some lose ends and little testing has been done on most of it. > > Thomas > > > On Sep 9, 2005, at 6:35 AM, Juergen Hoeller wrote: > > >> Everyone, >> >> I'm inclined to do a Spring 1.2.5 release before going for 1.3 RC1: >> resolving the already known issues in the 1.2.x line, as reported on >> our JIRA and partly already fixed in CVS (currently with target 1.3 >> RC1). The >> 1.2.5 release, if desired, would have to happen end of next week. >> Afterwards, CVS HEAD would be dedicated to 1.3 development, with a >> 1.2 >> maintenance branch alongside. >> >> Ideally, the 1.2.5 release would include all minor fixes done since >> 1.2.4 >> (there were quite a few, including javadoc fixes). Hence, I would >> like >> to create it from CVS HEAD rather than from a 1.2.4 branch. This >> means >> that already committed 1.3 features would have to be temporarily >> moved >> to the sandbox, unless we decide to release them in 1.2.5 already. >> >> The request log filter and named JDBC statement parameters are >> candidates for 1.2.5, I guess, as they have been planned for 1.2.x >> initially. >> Thomas, >> if you'd like to not release named JDBC statement parameters before >> 1.3 RC1, >> I would temporarily move it to the sandbox and back after the actual >> 1.2.5 release. I'll leave that decision up to you. >> >> Regards, >> >> Juergen >> >> ----- >> Juergen Hoeller >> Interface21 - Spring Services from the Source >> http://www.springframework.com >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is Sponsored by the Better Software Conference & EXPO >> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >> Practices Agile & Plan-Driven Development * Managing Projects & Teams >> * Testing & QA Security * Process Improvement & Measurement * >> http://www.sqe.com/ bsce5sf >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework- >> developer >> >> >> >> > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September > 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & > Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security > * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * > Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/ > bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > |
|
From: Juergen H. <ju...@in...> - 2005-09-09 22:41:05
|
Yes, I'm aware that this wasn't clear. I wanted to leave the option for a 1.2.5 release open but didn't clearly communicate that: I just told some people in private to keep definitive 1.3 stuff in the sandbox for the time being. So that was mainly a note to myself: I need to put definite announcements out when CVS HEAD moves on to the next major version, with a maintenance branch created for the previous version. I've just changed all version numbers to 1.2.5, so future nightly snapshots will have that name. I've also updated JIRA accordingly, separating 1.2.5 issues from 1.3 RC1 issues. BTW, additional tests and other stuff that does make sense for 1.2.x should stay in the main sources, as well as minor new stuff. It's really only definitive 1.3 features that should move to the sandbox. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Thomas Risberg Sent: Saturday, September 10, 2005 12:21 AM To: spr...@li... Subject: Re: [Springframework-developer] 1.2.5 release I'll move it over to the sandbox the next couple of days. 1.2.5 wasn't on the roadmap earlier so I went ahead with 1.3 features - I changed the version to 1.3-dev - we should change that to 1.2.5 so the downloadable nightly snapshots are named accordingly. Thomas On Sep 9, 2005, at 5:26 PM, Juergen Hoeller wrote: > Thomas, > > Do you have the chance to move those classes to the sandbox, > potentially holding the JdbcTemplate extensions in a special > JdbcTemplate subclass for the time being? I can do that move as well, > of course, but I don't want to infer with any local changes you might > already have made but not committed yet. > > In general, we should have clarified the role of CVS HEAD. We need > definitive announcements once HEAD turns to the next major release. > Currently it still serves as basis for 1.2.5, which will then lead to > a 1.2.x maintenance branch (for potential future patches), with CVS > HEAD becoming the basis for 1.3. > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On > Behalf Of Thomas Risberg > Sent: Friday, September 09, 2005 2:20 PM > To: spr...@li... > Subject: Re: [Springframework-developer] 1.2.5 release > > Juergen, > > I'd prefer to keep the named parameters for a 1.3RC1 release - there > are still some lose ends and little testing has been done on most of > it. > > Thomas > > > On Sep 9, 2005, at 6:35 AM, Juergen Hoeller wrote: > > >> Everyone, >> >> I'm inclined to do a Spring 1.2.5 release before going for 1.3 RC1: >> resolving the already known issues in the 1.2.x line, as reported on >> our JIRA and partly already fixed in CVS (currently with target 1.3 >> RC1). The >> 1.2.5 release, if desired, would have to happen end of next week. >> Afterwards, CVS HEAD would be dedicated to 1.3 development, with a >> 1.2 >> maintenance branch alongside. >> >> Ideally, the 1.2.5 release would include all minor fixes done since >> 1.2.4 >> (there were quite a few, including javadoc fixes). Hence, I would >> like to create it from CVS HEAD rather than from a 1.2.4 branch. This >> means that already committed 1.3 features would have to be >> temporarily moved to the sandbox, unless we decide to release them in >> 1.2.5 already. >> >> The request log filter and named JDBC statement parameters are >> candidates for 1.2.5, I guess, as they have been planned for 1.2.x >> initially. >> Thomas, >> if you'd like to not release named JDBC statement parameters before >> 1.3 RC1, >> I would temporarily move it to the sandbox and back after the actual >> 1.2.5 release. I'll leave that decision up to you. >> >> Regards, >> >> Juergen >> >> ----- >> Juergen Hoeller >> Interface21 - Spring Services from the Source >> http://www.springframework.com >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is Sponsored by the Better Software Conference & EXPO >> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >> Practices Agile & Plan-Driven Development * Managing Projects & Teams >> * Testing & QA Security * Process Improvement & Measurement * >> http://www.sqe.com/ bsce5sf >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework- >> developer >> >> >> >> > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices Agile & Plan-Driven Development * Managing Projects & Teams > * Testing & QA Security > * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices Agile & Plan-Driven Development * Managing Projects & Teams > * Testing & QA Security * Process Improvement & Measurement * > http://www.sqe.com/ bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Thomas R. <tho...@tr...> - 2005-09-11 15:54:04
|
I've reverted the named parameter changes. I'll add them to the sandbox when I get a chance. Thomas On Sep 9, 2005, at 6:40 PM, Juergen Hoeller wrote: > Yes, I'm aware that this wasn't clear. I wanted to leave the option > for a > 1.2.5 release open but didn't clearly communicate that: I just told > some > people in private to keep definitive 1.3 stuff in the sandbox for > the time > being. > > So that was mainly a note to myself: I need to put definite > announcements > out when CVS HEAD moves on to the next major version, with a > maintenance > branch created for the previous version. > > I've just changed all version numbers to 1.2.5, so future nightly > snapshots > will have that name. I've also updated JIRA accordingly, separating > 1.2.5 > issues from 1.3 RC1 issues. > > BTW, additional tests and other stuff that does make sense for > 1.2.x should > stay in the main sources, as well as minor new stuff. It's really only > definitive 1.3 features that should move to the sandbox. > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On > Behalf Of > Thomas Risberg > Sent: Saturday, September 10, 2005 12:21 AM > To: spr...@li... > Subject: Re: [Springframework-developer] 1.2.5 release > > I'll move it over to the sandbox the next couple of days. > > 1.2.5 wasn't on the roadmap earlier so I went ahead with 1.3 features > - I changed the version to 1.3-dev - we should change that to 1.2.5 > so the > downloadable nightly snapshots are named accordingly. > > Thomas > > On Sep 9, 2005, at 5:26 PM, Juergen Hoeller wrote: > > >> Thomas, >> >> Do you have the chance to move those classes to the sandbox, >> potentially holding the JdbcTemplate extensions in a special >> JdbcTemplate subclass for the time being? I can do that move as well, >> of course, but I don't want to infer with any local changes you might >> already have made but not committed yet. >> >> In general, we should have clarified the role of CVS HEAD. We need >> definitive announcements once HEAD turns to the next major release. >> Currently it still serves as basis for 1.2.5, which will then lead to >> a 1.2.x maintenance branch (for potential future patches), with CVS >> HEAD becoming the basis for 1.3. >> >> Juergen >> >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...] On >> Behalf Of Thomas Risberg >> Sent: Friday, September 09, 2005 2:20 PM >> To: spr...@li... >> Subject: Re: [Springframework-developer] 1.2.5 release >> >> Juergen, >> >> I'd prefer to keep the named parameters for a 1.3RC1 release - there >> are still some lose ends and little testing has been done on most of >> it. >> >> Thomas >> >> >> On Sep 9, 2005, at 6:35 AM, Juergen Hoeller wrote: >> >> >> >>> Everyone, >>> >>> I'm inclined to do a Spring 1.2.5 release before going for 1.3 RC1: >>> resolving the already known issues in the 1.2.x line, as reported on >>> our JIRA and partly already fixed in CVS (currently with target 1.3 >>> RC1). The >>> 1.2.5 release, if desired, would have to happen end of next week. >>> Afterwards, CVS HEAD would be dedicated to 1.3 development, with a >>> 1.2 >>> maintenance branch alongside. >>> >>> Ideally, the 1.2.5 release would include all minor fixes done since >>> 1.2.4 >>> (there were quite a few, including javadoc fixes). Hence, I would >>> like to create it from CVS HEAD rather than from a 1.2.4 branch. >>> This >>> means that already committed 1.3 features would have to be >>> temporarily moved to the sandbox, unless we decide to release >>> them in >>> 1.2.5 already. >>> >>> The request log filter and named JDBC statement parameters are >>> candidates for 1.2.5, I guess, as they have been planned for 1.2.x >>> initially. >>> Thomas, >>> if you'd like to not release named JDBC statement parameters before >>> 1.3 RC1, >>> I would temporarily move it to the sandbox and back after the actual >>> 1.2.5 release. I'll leave that decision up to you. >>> >>> Regards, >>> >>> Juergen >>> >>> ----- >>> Juergen Hoeller >>> Interface21 - Spring Services from the Source >>> http://www.springframework.com >>> >>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is Sponsored by the Better Software Conference & EXPO >>> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >>> Practices Agile & Plan-Driven Development * Managing Projects & >>> Teams >>> * Testing & QA Security * Process Improvement & Measurement * >>> http://www.sqe.com/ bsce5sf >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >>> >>> >>> >>> >> >> >> >> ------------------------------------------------------- >> SF.Net email is Sponsored by the Better Software Conference & EXPO >> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >> Practices Agile & Plan-Driven Development * Managing Projects & Teams >> * Testing & QA Security >> * Process Improvement & Measurement * http://www.sqe.com/bsce5sf >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework- >> developer >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is Sponsored by the Better Software Conference & EXPO >> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >> Practices Agile & Plan-Driven Development * Managing Projects & Teams >> * Testing & QA Security * Process Improvement & Measurement * >> http://www.sqe.com/ bsce5sf >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework- >> developer >> >> >> >> > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September > 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & > Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security > * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * > Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/ > bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > |
|
From: Juergen H. <ju...@in...> - 2005-09-11 20:29:40
|
Thanks, Thomas - and sorry for the inconvenience. Developers: There are still a few issues open for 1.2.5, as listed in JIRA. Everything major should have been addressed already; we're waiting for user feedback on a couple of things. However, it would be great if we could address some of the open minor things as well - in the course of this week. Everybody: I would appreciate tests of current nightly 1.2.5 snapshots! Even plain sanity checking would be helpful: e.g. dropping the snapshot spring.jar into your application's integration test suite and seeing whether everything still passes - no matter which Spring 1.2.x version you're currently using. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Thomas Risberg Sent: Sunday, September 11, 2005 5:55 PM To: spr...@li... Subject: Re: [Springframework-developer] 1.2.5 release I've reverted the named parameter changes. I'll add them to the sandbox when I get a chance. Thomas On Sep 9, 2005, at 6:40 PM, Juergen Hoeller wrote: > Yes, I'm aware that this wasn't clear. I wanted to leave the option > for a > 1.2.5 release open but didn't clearly communicate that: I just told > some people in private to keep definitive 1.3 stuff in the sandbox for > the time being. > > So that was mainly a note to myself: I need to put definite > announcements out when CVS HEAD moves on to the next major version, > with a maintenance branch created for the previous version. > > I've just changed all version numbers to 1.2.5, so future nightly > snapshots will have that name. I've also updated JIRA accordingly, > separating > 1.2.5 > issues from 1.3 RC1 issues. > > BTW, additional tests and other stuff that does make sense for 1.2.x > should stay in the main sources, as well as minor new stuff. It's > really only definitive 1.3 features that should move to the sandbox. > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On > Behalf Of Thomas Risberg > Sent: Saturday, September 10, 2005 12:21 AM > To: spr...@li... > Subject: Re: [Springframework-developer] 1.2.5 release > > I'll move it over to the sandbox the next couple of days. > > 1.2.5 wasn't on the roadmap earlier so I went ahead with 1.3 features > - I changed the version to 1.3-dev - we should change that to 1.2.5 so > the downloadable nightly snapshots are named accordingly. > > Thomas > > On Sep 9, 2005, at 5:26 PM, Juergen Hoeller wrote: > > >> Thomas, >> >> Do you have the chance to move those classes to the sandbox, >> potentially holding the JdbcTemplate extensions in a special >> JdbcTemplate subclass for the time being? I can do that move as well, >> of course, but I don't want to infer with any local changes you might >> already have made but not committed yet. >> >> In general, we should have clarified the role of CVS HEAD. We need >> definitive announcements once HEAD turns to the next major release. >> Currently it still serves as basis for 1.2.5, which will then lead to >> a 1.2.x maintenance branch (for potential future patches), with CVS >> HEAD becoming the basis for 1.3. >> >> Juergen >> >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...] On >> Behalf Of Thomas Risberg >> Sent: Friday, September 09, 2005 2:20 PM >> To: spr...@li... >> Subject: Re: [Springframework-developer] 1.2.5 release >> >> Juergen, >> >> I'd prefer to keep the named parameters for a 1.3RC1 release - there >> are still some lose ends and little testing has been done on most of >> it. >> >> Thomas >> >> >> On Sep 9, 2005, at 6:35 AM, Juergen Hoeller wrote: >> >> >> >>> Everyone, >>> >>> I'm inclined to do a Spring 1.2.5 release before going for 1.3 RC1: >>> resolving the already known issues in the 1.2.x line, as reported on >>> our JIRA and partly already fixed in CVS (currently with target 1.3 >>> RC1). The >>> 1.2.5 release, if desired, would have to happen end of next week. >>> Afterwards, CVS HEAD would be dedicated to 1.3 development, with a >>> 1.2 >>> maintenance branch alongside. >>> >>> Ideally, the 1.2.5 release would include all minor fixes done since >>> 1.2.4 >>> (there were quite a few, including javadoc fixes). Hence, I would >>> like to create it from CVS HEAD rather than from a 1.2.4 branch. >>> This >>> means that already committed 1.3 features would have to be >>> temporarily moved to the sandbox, unless we decide to release them >>> in >>> 1.2.5 already. >>> >>> The request log filter and named JDBC statement parameters are >>> candidates for 1.2.5, I guess, as they have been planned for 1.2.x >>> initially. >>> Thomas, >>> if you'd like to not release named JDBC statement parameters before >>> 1.3 RC1, >>> I would temporarily move it to the sandbox and back after the actual >>> 1.2.5 release. I'll leave that decision up to you. >>> >>> Regards, >>> >>> Juergen >>> >>> ----- >>> Juergen Hoeller >>> Interface21 - Spring Services from the Source >>> http://www.springframework.com >>> >>> >>> >>> >>> ------------------------------------------------------- >>> SF.Net email is Sponsored by the Better Software Conference & EXPO >>> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >>> Practices Agile & Plan-Driven Development * Managing Projects & >>> Teams >>> * Testing & QA Security * Process Improvement & Measurement * >>> http://www.sqe.com/ bsce5sf >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >>> >>> >>> >>> >> >> >> >> ------------------------------------------------------- >> SF.Net email is Sponsored by the Better Software Conference & EXPO >> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >> Practices Agile & Plan-Driven Development * Managing Projects & Teams >> * Testing & QA Security >> * Process Improvement & Measurement * http://www.sqe.com/bsce5sf >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework- >> developer >> >> >> >> >> ------------------------------------------------------- >> SF.Net email is Sponsored by the Better Software Conference & EXPO >> September 19-22, 2005 * San Francisco, CA * Development Lifecycle >> Practices Agile & Plan-Driven Development * Managing Projects & Teams >> * Testing & QA Security * Process Improvement & Measurement * >> http://www.sqe.com/ bsce5sf >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework- >> developer >> >> >> >> > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices Agile & Plan-Driven Development * Managing Projects & Teams > * Testing & QA Security > * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices Agile & Plan-Driven Development * Managing Projects & Teams > * Testing & QA Security * Process Improvement & Measurement * > http://www.sqe.com/ bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
