10:31 a.m.
I'm a connector developer and this release was not immaterial from my perspective, its
an embarrassment. NONE of my stuff works. And just to be clear, this is not because of
any defect in Teiid, but because of Designer problems that I identified too late to get
fixed.
But you know what, I don't care, it's done. I'm asking about 6.1. What are
we going to differently for 6.1 to produce a release that is interesting and meaningful to
users. Unless we patch the 6.0.0 Designer, which we don't want to do, you won't
be able to use any of my connectors with a 6.0.0 Designer and a 6.1 Teiid either. So we
have to get 6.1 Teiid to work with 6.1 Designer as I see it.
I've already stated how I think we should do this, leave Teiid in the unstable bucket
until we have validated that Teiid and Designer work together. Then move them both to
stable, which is the new 'GA'. How you you all think we should accomplish this?
~jd
----- "Steven Hawkins" <shawkins(a)redhat.com> wrote:
What seems to be disturbing everyone is what the definition of a
community release is. Ultimately that's up to the community, so kudos
to us for having this discussion. Also, I don't take John's comment
below as inflammatory, rather many of you heard me say the same prior
to open sourcing that notion of a Teiid only initial release was
immaterial from the perspective of most end users (but not connector
developers).
In a perfect world with respect to initial community releases, they
would have been done at the edge of a productization cycle. Our
timing was instead to go open source (or at least make public
announcements) in the middle of a development cycle. The 6.0.0
release of Teiid from an product perspective would be a milestone, but
was done for the community for two reasons. First it was considered
desirable to have a release close to the project announcement date.
The other reason, which is more important, was to establish the
independent nature of Teiid development. We may not all agree with
those points, but there it stands.
To sum up the best parts of this discussion:
Does the Teiid 6.0.0 release matter to most users - Not really.
Will there be synchronization between future Teiid and Teiid Designer
releases - Not really.
Will we be in the habit of patch releases - Not really.
Do we need modularize our software more - Yes. A better separation of
Teiid Designer's usage of Teiid's code, separating out projects for
"large" connectors, soap services, etc.
All need to be explored. We've made the jump from 1 code base to 3,
we can do more if needed.
----- Original Message -----
From: "John Verhaeg" <jverhaeg(a)redhat.com>
To: "John Doyle" <jdoyle(a)redhat.com>
Cc: teiid-designer-dev(a)lists.jboss.org, teiid-dev(a)lists.jboss.org,
"Van Halbert" <vhalbert(a)redhat.com>, "Steven Hawkins"
<shawkins(a)redhat.com>
Sent: Thursday, April 23, 2009 10:36:19 AM GMT -06:00 US/Canada
Central
Subject: Re: [teiid-designer-dev] Re: [teiid-dev] 6.1 Release
On Apr 23, 2009, at 10:29 AM, John Doyle wrote:
>
> I agree with this as long as the predicate is that there is a
> version of tooling (Designer or other) that we have validated to
> work with the Teiid release (excepting the new features in the Teiid
> release as you described above).
>
Agreed. That's why I'm pretty much considering Teiid as a whole as
unreleased, regardless of what version the Teiid Server team is
working on. The difficult part is figuring out a way to convey this
effectively to the community. Backing off a little on what I said
before, it certainly would have been ideal in my mind if the very
first version of Teiid wasn't released until Designer was ready, but
that ship has sailed.
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev
--
John Doyle
Senior Software Engineer
JBoss, a division of Red Hat
Office: 978.392.3916
Email: jdoyle(a)redhat.com