2.7 Consensus

[Martin Baxter]

Scott Kane wrote:
> Hi all,
> 
> There has been a lot of chatter here (in a good way)
> about the release of 2.7.  I'm eligible for the
> upgrade and have downloaded it and so far have had
> zero problems in the tasks I have needed to perform.
> 
> However - I'm leery on working on a project for real
> given some of the issues being raised (and the statements
> from some old hands that they have reverted back to 2.6.*)
> and am looking for something positive before committing
> to it.  I'd welcome your input on this....
> 
> Scott

Hi Scott

I doubt there could be consensus on this because the answer is so
dependent on individual needs. Some reasons for not upgrading that I can
think of are:

1) you have a shipping product to support and some particular aspect of
2.7 causes problems.

2) you make rev plugins and libraries that must be backwards compatible
for users who have not upgraded (though you *can* make these with 2.7,
it is not officially supported for some reason)

3) There is currently a deficiency with 2.7 that is a blocker for your
own projects, e.g. lack of MacOS 9 support, so you are better waiting
until that appears.

In my own case, I work on one project, which is an in-house tool. It's
well established, and fairly large and therefore time consuming to test
thoroughly. So I would be wary of irrevocably switching to a new version
of Rev without an extended period of testing in which I use both old and
new versions concurrently, (preferably on separate machines) until I am
sure enough of the new version to commit to it.

["My "|""]twopennuth

Martin Baxter