We've talked about it in the past. There are a number of projects that are already DB focused.
OpenJPA (if there is ever a code commit) will likely displace the TranQL persistence piece. The
connectors are still valid and may find a home here. I think we need to let the dust settle before
we move it though.
Matt
Zakharov, Vasily M wrote:
Matt,
By the way, are there any plans to make TranQL an Apache project, or
even a Geronimo component?
Vasily Zakharov
Intel Middleware Products Division
-----Original Message-----
From: Matt Hogstrom [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 6:54 AM
To: [email protected]
Subject: Re: 1.1 Final Items
TranQL has three components. The Connectors (1.2-SNAPSHOT), the
persistence engine (1.3-SNAPSHOT)
and the vendors rars (various versions depending on the rar in
question).
Does that answer your question ?
Matt
Jason Dillon wrote:
Why 2 versions of TranQL?
--jason
On 5/31/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
Here are the outstanding issues and my proposed plans to finish 1.1.
Currently there are 124 JIRAs out there for 1.1. There are also 7 or
8 blockers. I have not seen
any activity on these items in the last week so I'm assuming that
there is no resource to fix them.
I propose that tomorrow I'll move the JIRA's in 1.1 to 1.2 and for
those items that are considered
hot and people want to work on them they can move them to the 1.1.1
release. I'll do this through a
bulk change.
The remaining items are:
Convert remaining SNAPSHOTs to releases. Here is the remaining list
of items:
activemq_version=3.2.4-SNAPSHOT
geronimo_version=1.1-SNAPSHOT
openejb_version=2.1-SNAPSHOT
tranql_version=1.2-SNAPSHOT
tranql_version=1.3-SNAPSHOT
geronimo_spec_corba_version=1.0-SNAPSHOT
geronimo_spec_j2ee_version=1.1-SNAPSHOT
geronimo_spec_javamail_version=1.1-SNAPSHOT
geronimo_spec_jcache_version=1.1-SNAPSHOT
daytrader_version=1.1-SNAPSHOT
I will convert DayTrader and TranQL after the final set of stress
testing.
Any volunteers to convert the specs? (Alan :)
Kevan, we'll need you to sign off on the activemq versions.
When the above is complete I suggest we get a final test from Kevan
and cut a proposed 1.1 for Friday.
If that's good (or if there are only minor fixes) we'll push 1.1 out
next week and then move on to
1.2 and beyond.
Thoughts?
Matt
