7:58 p.m.
I'm not sure there's a response to my concern in your response.
I'm aware that there's an aggressive schedule, but I question that value of
releasing Teiid on it's projected release date, if the Designer is not ready to
release, or vice versa. I have changes coming in 6.1 to connectors that are depending
upon importer changes. I can mock up tests for the connector changes, but I won't
really be able to validate a feature until I have two stable projects in my hands that are
pretty much locked down.
We can call them independent all we want, users will disagree. There's already
traffic on the lists to demonstrate that.
What's wrong with leaving it on the shelf until both are ready, and then making it
official?
~jd
----- "Steven Hawkins" <shawkins(a)redhat.com> wrote:
>From here out the versions of Teiid and Teiid Designer are
independent. The 6.0 release of Designer currently corresponds to
Teiid 6.0 + patches. We will release a Teiid 6.0.1 if necessary to
support the Designer, but the current thought is just to wrap up Teiid
6.1.0 in the near term. Teiid Designer has an aggressive schedule for
their 6.1 release, but there's no guarantee that it will be extremely
close to Teiid 6.1.0.
----- Original Message -----
From: "John Doyle" <jdoyle(a)redhat.com>
To: teiid-dev(a)lists.jboss.org, teiid-designer-dev(a)lists.jboss.org
Sent: Wednesday, April 22, 2009 4:26:15 PM GMT -06:00 US/Canada
Central
Subject: [teiid-dev] 6.1 Release
I'm having issues testing the 6.0 release and I want to ensure that we
have a plan for 6.1 to address the issues I'm having.
The challenge is this. Teiid 6.0 was released on the 23rd of March.
The 6.0 Designer release is just now wrapping up - a month later.
It's difficult to accurately determine the quality of connectors
delivered in 6.0 until the Designer is finished and I can create the
models that the connectors consume. This is particularly accute when
there is a strong connector dependency on importer-produced metadata
(such as XML-Relational and Salesforce.com connectors).
Are we planning on releasing Teiid Designer and Teiid together (or
extremely close) for 6.1?
I've copied both dev lists to ensure that both projects are included.
~jd
--
John Doyle
Senior Software Engineer
JBoss, a division of Red Hat
Office: 978.392.3916
Email: jdoyle(a)redhat.com
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev
_______________________________________________
teiid-designer-dev mailing list
teiid-designer-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
10:42 p.m.
New subject: [teiid-designer-dev] Re: 6.1 Release
On Wed, 2009-04-22 at 20:58 -0400, John Doyle wrote:
I'm aware that there's an aggressive schedule, but I question that
value of releasing Teiid on it's projected release date, if the
Designer is not ready to release, or vice versa.
Release soon and release often is the mantra for JBoss. I do not believe
either that they should be tightly dependent on release on each other
either. It would hard to adjust each others feature bucket, just so that
they can be released together. Just think about the lost time for the
team waiting.
For this exact purpose we are creating branch (for example 6.0.x), if
you are looking for a stable branch to make such changes. Then it is up
us to either cut a patch or cut another release based on amount of
changes.
Platform releases, that tie all of them together.
I have changes coming in 6.1 to connectors that are depending upon
importer changes. I can mock up tests for the connector changes, but
I won't really be able to validate a feature until I have two stable
projects in my hands that are pretty much locked down.
I understand, what you are saying, but instead of working around it, we
need to fix it. If you saying that we have connector changes that are
dependent upon tooling code to the runtime code, I we need to
a) better plan according to upcoming releases
b) decouple dependencies, use better abstractions
c) modularize
on these fronts we have stepped up and we need to to continue to push
further. Lets think in these terms and see if we can reduce this for
future releases. Can XML importer plugin can be deployed on its own
without Designer stuff?
We can call them independent all we want, users will disagree.
There's already traffic on the lists to demonstrate that.
The current release we are going through lot of connector type
definition changes, once we stabilize embedded integration and connector
integration this should reduced greatly, unless we change the vdb
indexing. We got JIRAs for lot of these already.
Ramesh..
5721
days inactive
5721
days old
1 comments
2 participants
participants (2)
-
John Doyle -
Ramesh Reddy