There's been no opposition from St. Louis devs, so that seems like a consensus.
I'll update JIRA and we'll look for doing 7.0 MS 1 on Monday!
----- Original Message -----
From: "Ken Johnson" <kejohnso(a)redhat.com>
To: "Steven Hawkins" <shawkins(a)redhat.com>
Cc: "teiid-dev" <teiid-dev(a)lists.jboss.org>
Sent: Thursday, November 12, 2009 10:36:19 AM GMT -06:00 US/Canada Central
Subject: Re: [teiid-dev] 6.3 vs 7.0
I agree with moving 6.3 -> 7.0 and current 7.x -> 8.x. The release
cycle lengthening also makes sense.
-Ken
Steven Hawkins wrote:
Hello all,
Given the scope of changes for 6.3 (metadata changes that are already in, container and
caching changes that are pending) there is case to be made for promoting 6.3 to be the 7.0
release. Most of the existing 7.0/7.x issues would then become part of an 8.x release.
The 7.x release line (7.1, etc.) would further refine the new deployment model and
continue to make targeted, rather than sweeping, query changes. If we make the change to
7.0, I would also propose lengthening the release cycle out to Jan 8th to allow for more
changes and testing that would be expected with a major release number.
Regardless we will look at getting a milestone out this week to promote usage of the
changes made to date.
Does anyone feel strongly one way or another?
Steve
_______________________________________________
teiid-dev mailing list
teiid-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-dev
--
Ken Johnson
Sr. Product Manager
JBoss Middleware Business Unit
Red Hat, Inc
978.392.3917
ken.johnson(a)redhat.com