nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Technical Support of Teamsite 5.5.2

Martha

I was wondering if there was ever an official date announced as to when IW will no longer support Teamsite, version 5.5 (we have 5.5.2).

Find more posts tagged with

Comments

Adam Stoller

I believe the date is sometime in June 2005 - there was a thread about this not tooo long ago - if you search the forumns for "June 2005" (with AND) - you should be able to find it.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

The end-of-life announcements are kept on the support web site.

Here's the link to it:
https://support.interwoven.com/notifications/default.asp

Note that you can always find this by navigation from the main support site: click "notifications" in the "more" box.

And, what this notification says for TeamSite 5.5.x is the following:
We are announcing the final year of support for TeamSite 5.5.x, TeamSite and Templating 5.5.x. Support for these products will end June 30, 2005, which is 21 months after the release of TeamSite 6.

Regards,

lissa

nipper

Lissa

Is there any written policy about bugfixes/enhancements to 5.5.2 ? I suspect the
odds of an enhancement are none & bugs need to be extremely high priority.

I would appreciate any details

Andy

Migrateduser

>Support for these products will end June 30, 2005, which is 21 months after the release of TeamSite 6.

Can the support policy be changed from "release" to "viability of"?

nipper

>Can the support policy be changed from "release" to "viability of"?

Sure

Depends on your definition of viability.

On a CD ? Viable.

Migrateduser

The hard part of this for me to swallow is that Interwoven knew that 6.0 was ****. In fact, they were already planning the 6.1 release to be a bug fix release less than a month after 6.0 was released. I can't believe anyone was using 6.0 in production at any time. To use the release of 6.0 as a gauge for determining when to end-of-life the last stable release prior to it is poor judgement, in my opinion. The only 6.x release that's remotely stable is 6.1. The EOL plan for 5.5 is very aggressive - what's the hurry?

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

johnjamesmarsh

My users are a little reluctant to migrate to 6 as it means a total retraining of all the users and re-engineering of their solution. There is no easy route to 6.x and the business men keep asking "What am I paying for this migration for?" The product is free but the retraining of a very non-techincal userbase is not.

Migrateduser

Couldn't agree more. Interwoven is not paying attention to their customers. To end-of-life the last stable version only 18 months after a drastically new UI is released is poor judgement. Other releases have been supported for a lot longer than this, and like you, many customers appear to be very hesitant to take the plunge to 6.1. The training issues are our biggest hurdles as well. We just don't have a lot of resources to train all our users very quickly. I think Intwerwoven needs to open up its customer surveys to a broader set if customers.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

nipper

The funny thing I heard was the part of the rationale is that no one uses WebDesk (except my 200 users I guess)
& that replacing WD should not be a big issue.

HA

Migrateduser

> The EOL plan for 5.5 is very aggressive - what's the hurry?

If they rush you, you have less time to consider lower total cost of ownership/higher ROI alternatives.