Vote passed, unanimous +1s. (I just hope I identified roles correctly
below...)
http://people.apache.org/~jim/projects.html#commons
Joerg Schaible (Commons PMC)
Dan Fabulich (Commons Committer)
Liam Coughlin
Dave Miekle
Henri Yandell (Commons PMC)
Phil Steitz (Commons PMC)
Dan Fabulich
Dan Fabulich wrote at Donnerstag, 16. April 2009 22:06:
We have a +1 from Liam Coughlin, but still need two more binding (PMC) +1s
to release.
No, you had two +1 from Liam and me.
- Jörg
-
To unsubscribe, e-mail:
Henri Yandell wrote:
+1 from me.
sigs pass. source happily rebuilds. release notes matches JIRA.
license/notice look good.
items in release notes all look good.
+1
Phil
-
To unsubscribe, e-mail:
+1 from me.
sigs pass. source happily rebuilds. release notes matches JIRA.
license/notice look good.
items in release notes all look good.
Hen
2009/3/15 Dan Fabulich d...@fabulich.com
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because
We have a +1 from Liam Coughlin, but still need two more binding (PMC) +1s
to release.
-Dan
Dan Fabulich wrote:
Took me a few weeks, but I finally got around to installing a free instance
of Oracle (Express Edition 10.2) and testing the null handling code we
introduced in DbUtils 1.2
Hi,
2009/3/15 Dan Fabulich d...@fabulich.com
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because
Finally, had a chance to look at this and its a +1 from me.
Cheers,
Dave
Took me a few weeks, but I finally got around to installing a free
instance of Oracle (Express Edition 10.2) and testing the null handling
code we introduced in DbUtils 1.2 (DBUTILS-31).
Sure enough, there's a bug, DBUTILS-55, but I don't think it's very
important, since it's not a
+1, source tarball can be used to build package will all my different
compilers, all tests pass.
- Jörg
Dan Fabulich wrote:
My third attempt at releasing a commons project; please test rigorously!
RC3 includes an API change to QueryRunner to guarantee thread-safety.
(DBUTILS-52)
NOTE:
sebb wrote:
On 15/03/2009, Dan Fabulich d...@fabulich.com wrote:
The problem gets even more complicated if we tried to write a generic
IntegrationTestApp to work against multiple vendors. How would the
IntegrationTestApp know what column types are possible? How would it manage
access to the
On 16/03/2009, Dan Fabulich d...@fabulich.com wrote:
sebb wrote:
On 15/03/2009, Dan Fabulich d...@fabulich.com wrote:
The problem gets even more complicated if we tried to write a generic
IntegrationTestApp to work against multiple vendors. How would the
IntegrationTestApp know
Why can't our test suite include some hsqldb-based tests? We do that at
work to test our hibernate queries and stuff. Each test case class gets
their own in-memory database. Performance isn't an issue
On Mar 15, 2009 3:10 PM, Dan Fabulich d...@fabulich.com wrote:
My third attempt at
Unless something has changed, the current test cases do include hsqldb based
tests.
The specific issue is that some of the changes in the proposed 1.2 have a
specific impact on specific databases ( notably, oracle ) -- so it would be
extremely useful if someone who has some access to some oracle
My third attempt at releasing a commons project; please test rigorously!
RC3 includes an API change to QueryRunner to guarantee thread-safety.
(DBUTILS-52)
NOTE: No one has yet explicitly said on-list that they have tested DbUtils
1.2 with a real database. We should not release it until
On 15/03/2009, Dan Fabulich d...@fabulich.com wrote:
My third attempt at releasing a commons project; please test rigorously!
RC3 includes an API change to QueryRunner to guarantee thread-safety.
(DBUTILS-52)
NOTE: No one has yet explicitly said on-list that they have tested DbUtils
1.2
sebb wrote:
On 15/03/2009, Dan Fabulich d...@fabulich.com wrote:
PLEASE TEST THIS RELEASE WITH A REAL DATABASE!
Although this project has reasonable unit tests, it has no integration
tests with any actual databases; it is quite possible that the fix for
DBUTILS-31 has broken something on
sebb wrote:
Having a ready-made test app might encourage others to test as well.
What do you have in mind here? An OracleTestApp class checked into our
tests? Or an IntegrationTestApp that would work against multiple
vendors?
I can certainly imagine an OracleTestApp, but naturally I'm
On 15/03/2009, Dan Fabulich d...@fabulich.com wrote:
sebb wrote:
Having a ready-made test app might encourage others to test as well.
What do you have in mind here? An OracleTestApp class checked into our
tests? Or an IntegrationTestApp that would work against multiple vendors?
I
17 matches
Mail list logo