Let's create a branch in the sandbox and let Dan dive in. Effectively
it's the git model, but slightly closer because he's already a
committer. Once it's reached its release point, we can all be looking
and debating whether it is DbUtils 2.0 or DbUtils2.
[The first is a new release of the existing
So how do we want to handle this? Happy to give you sandbox access.
That said it should probably better be a branch on the DbUtils project.
And as a side note: I doubt folks here will sign off on a release that
changes the java target version in a minor version change ;)
cheers
--
Torsten
On Sa
On 2009-02-07, Dan Fabulich wrote:
> Assuming I don't yet have karma to write to the sandbox, may I
> politely ask someone to grant it to me?
Should be done now.
Stefan
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.
On Sat, Feb 7, 2009 at 2:16 AM, Dan Fabulich wrote:
> Rahul Akolkar wrote:
>
>> Help is usually quite welcome, the sandbox is open to all Apache
>> committers. Ofcourse, [dbutils] isn't in the sandbox -- though you
>> should be able to start a JDK 1.5 branch in the sandbox if you want.
>
> Do you
Rahul Akolkar wrote:
Help is usually quite welcome, the sandbox is open to all Apache
committers. Ofcourse, [dbutils] isn't in the sandbox -- though you
should be able to start a JDK 1.5 branch in the sandbox if you want.
Do you mean that, as an Apache committer, I already have sandbox karma?
On Thu, Feb 5, 2009 at 11:35 AM, Dan Fabulich wrote:
>
> I just submitted a big patch to DbUtils to update the API to use Java 5
> features (generics, varargs).
>
> http://issues.apache.org/jira/browse/DBUTILS-48
>
> There really aren't very many bugs left in this project; almost all of them
> hav
I just submitted a big patch to DbUtils to update the API to use Java 5
features (generics, varargs).
http://issues.apache.org/jira/browse/DBUTILS-48
There really aren't very many bugs left in this project; almost all of
them have patches attached. I think it wouldn't be much work for someb
