Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Tomahawk compatibility table
Date: Fri, 1 Feb 2008 15:01:16 -0500
Message-ID: <5E854482664CFB4E9FD6FF177BDBF6EA017C6F96@PHSXMB4.partners.org>
In-Reply-To: <3617095.1201871214521.JavaMail.root@viefep15>
Thread-Topic: Tomahawk compatibility table
Thread-Index: AchlDTMJMt69PMN8QUq1sY1zC76sYA==
From: "Barbalace, Richard" <RBARBALACE@PARTNERS.ORG>
To: <dev@myfaces.apache.org>
Cc: "Simon Kitching" <simon.kitching@chello.at>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am disappointed by the attitude expressed here.  Testing whether two rela=
ted
projects are compatible should be a basic part of the release process.  It =
is
simple QA.  That so many releases have gone through without such an essenti=
al
check raises questions about the competence of those involved in this proje=
ct.

Since Tomahawk 1.1.3 and Core 1.1.4, there have been several releases of ea=
ch.
Just finding a compatible pair of versions is a daunting task for anyone gi=
ven
the number of possible combinations, especially when trying to adjust for
incompatible changes among the versions of each project.  I have not yet fo=
und a
single match of newer versions of Tomahawk and Core that are compatible.  H=
aving
used MyFaces for three years now, I can safely say that leaving this import=
ant
task to even less experienced users is ridiculous.  The developers need to =
take
responsibility for their work.

Richard J. Barbalace
Boston, MA, USA=20


> -----Original Message-----
> From: Simon Kitching [mailto:simon.kitching@chello.at]=20
> Sent: Friday, February 01, 2008 8:07 AM
> To: dev@myfaces.apache.org
> Subject: Tomahawk compatibility table
>=20
>=20
> Hi,
>=20
> I'm getting really annoyed with all the "why isn't the=20
> tomahawk compatibility table up to date" questions.
>=20
> Unless someone vetos it, I'll just rip that page out of the=20
> site tonight, and put the existing info up on the wiki=20
> instead. Then users have only themselves to blame if it is=20
> not up-to-date.
>=20
> Regards, Simon
>=20

The information transmitted in this electronic communication is intended on=
ly
for the person or entity to whom it is addressed and may contain confidenti=
al
and/or privileged material. Any review, retransmission, dissemination or ot=
her
use of or taking of any action in reliance upon this information by persons=
 or
entities other than the intended recipient is prohibited. If you received t=
his
information in error, please contact the Compliance HelpLine at 800-856-198=
3 and
properly dispose of this information.